Ispzu 230
Ispzu 230
Ispzu 230
SC34-4823-03
Interactive System Productivity Facility (ISPF)
SC34-4823-03
Note
Before using this document, read the general information under “Notices” on page 495.
Internet: comments@us.ibm.com
If you would like a reply, be sure to include your name, address, telephone number, e-mail address, or FAX
number.
Make sure to include the following in your comment or note:
Title and order number of this document
Page number or topic related to your comment
The ISPF development team maintains a site on the World Wide Web. The URL for the site is:
http://www.ibm.com/software/awdtools/ispf/
© Copyright International Business Machines Corporation 1980, 2004. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Figures . . . . . . . . . . . . . . vii Chapter 3. View (Option 1) . . . . . . 85
View Entry Panel Action Bar . . . . . . . . 86
Tables . . . . . . . . . . . . . . . xi View Entry Panel Fields . . . . . . . . . . 87
Browsing a Data Set . . . . . . . . . . . 88
Ending Browse . . . . . . . . . . . . 88
Preface . . . . . . . . . . . . . . xiii
Browse Primary Commands . . . . . . . . 89
About This Document . . . . . . . . . . xiii
Who Should Use This Document . . . . . . . xiii
What Is In This Document . . . . . . . . . xiii Chapter 4. Edit (Option 2) . . . . . . 101
Using LookAt to look up message explanations . . xiv Editing a Data Set . . . . . . . . . . . . 102
Edit Entry Panel Action Bar . . . . . . . 102
Edit Entry Panel Fields . . . . . . . . . 103
Summary of Changes . . . . . . . . xv
ISPF Product and Library changes . . . . . .
. xv
ISPF Dialog Manager component changes . . .
. xv Chapter 5. Utilities (Option 3) . . . . 107
Dialog Tag Language (DTL) changes . . . . . xvi Utility Selection Panel Action Bar . . . . . . . 107
ISPF PDF Component changes . . . . . . . . xvi Library Utility (Option 3.1) . . . . . . . . . 108
ISPF SCLM Component changes . . . . . . . xvi Library Utility Panel Action Bar . . . . . . 108
ISPF Client/Server Component changes . . . . xvii Library Utility Panel Fields . . . . . . . . 109
ISPF Migration Considerations . . . . . . . xvii Library Utility Options for Data Sets . . . . 109
Library Utility Options for Members . . . . 118
Data Set Utility (Option 3.2) . . . . . . . . 119
What’s in the z/OS V1R6.0 ISPF
Data Set Utility Panel Action Bar . . . . . . 120
library? . . . . . . . . . . . . . . xix Data Set Utility Panel Fields . . . . . . . 120
z/OS V1R6.0 ISPF . . . . . . . . . . . . xix Data Set Utility Options . . . . . . . . . 121
Move/Copy Utility (Option 3.3) . . . . . . . 142
Part 1. ISPF Options . . . . . . . . 1 Move/Copy Utility Panel Action Bar . . . . 143
Move/Copy Utility Panel Fields . . . . . . 143
Move/Copy Utility Options . . . . . . . 144
Chapter 1. Primary Option Menu (POM) 5
Data Set List Utility (Option 3.4) . . . . . . . 150
The Primary Option Menu panel . . . . . . . 5
Data Set List Utility Panel Action Bar . . . . 150
ISPF Primary Options . . . . . . . . . . 5
Data Set List Utility Panel Fields . . . . . . 151
Primary Option Menu Action Bar Choices . . . 6
Data Set List Utility Options . . . . . . . 156
Status Area on the Primary Option Menu . . . . . 9
Data Set List Utility Line Commands . . . . 169
Status Pull-Down . . . . . . . . . . . . 9
Data Set List Utility Primary Commands . . . 176
Defining the Status Area . . . . . . . . . 16
Reset ISPF Statistics Utility (Option 3.5) . . . . 183
Reset ISPF Statistics Panel Action Bar . . . . 184
Chapter 2. Settings (Option 0) . . . . . 25 Reset ISPF Statistics Panel Fields . . . . . . 184
ISPF Settings Panel Fields . . . . . . . . . 26 Reset ISPF Statistics Utility Options . . . . . 185
Select Options . . . . . . . . . . . . 26 Hardcopy Utility (Option 3.6) . . . . . . . . 187
Terminal Characteristics . . . . . . . . . 30 Hardcopy Utility Panel Action Bar . . . . . 187
Print Graphics Parms . . . . . . . . . . 31 Hardcopy Utility Panel Fields . . . . . . . 188
General . . . . . . . . . . . . . . . 33 Generating and Submitting JCL . . . . . . 188
ISPF Settings Panel Action Bar . . . . . . . . 33 Additional Batch Printing Information . . . . 190
Specifying Log and List Defaults and Using the TSO/E Information Center Facility 190
Characteristics (The Log/List Action Bar Choice) . 35 Download Data Set to Workstation Utility (Option
Working with Function Keys and Keylists (The 3.7) . . . . . . . . . . . . . . . . . 192
Function Keys Action Bar Choice) . . . . . . 41 Download ISPF C/S component . . . . . . 192
The Function Keys Pull-Down . . . . . . . 56 Download/upload data set . . . . . . . . 196
Changing Default Colors (The Colors Action Bar Outlist Utility (Option 3.8) . . . . . . . . . 197
Choice) . . . . . . . . . . . . . . . 57 Outlist Utility Panel Action Bar . . . . . . 198
Specifying ISPF ENVIRON Settings (The Environ Outlist Utility Panel Fields . . . . . . . . 198
Action Bar Choice) . . . . . . . . . . . 64 Outlist Utility Options . . . . . . . . . 199
Specifying Workstation Parameters (The Command Table Utility (Option 3.9) . . . . . . 200
Workstation Action Bar Choice) . . . . . . . 65 Command Table Utility Panel Fields . . . . . 201
Specifying Message, Panel and Screen identifiers 79 Scrolling a Command Table . . . . . . . 203
Saving a Command Table . . . . . . . . 203
Contents v
Member Summary Listing . . . . . . . . . 474 UPDLDEL—Update Long Source and Delta
Summary and Statistics/PDS Overall Totals . . 474 Data Set . . . . . . . . . . . . . . 485
Bottom-of-Listing Information . . . . . . . . 475 UPDPDEL—Prefixed Delta Lines . . . . . . 486
Y2K Comparison . . . . . . . . . . . . 476 UPDREV—Update Revision . . . . . . . 487
Side-By-Side Listings . . . . . . . . . . . 476 UPDREV2 - Update Revision (2) . . . . . . 489
Effect of File Compare Type on SuperC Listings 477 UPDSEQ0—Update Sequenced 0 . . . . . . 489
File Comparison of a Sequential Data Set or UPDSUMO—Update Summary Only . . . . 490
Membered PDS . . . . . . . . . . . . 478
File Comparison of a Complete PDS . . . . . 478 Notices . . . . . . . . . . . . . . 495
Search-For Listings . . . . . . . . . . . 479 Programming Interface Information . . . . . . 496
Update Data Set Control Output Examples . . . 480 Trademarks . . . . . . . . . . . . . . 497
APNDUPD—Append Update Data Set . . . . 480
UPDCMS8—Update CMS Sequenced 8 . . . . 481
Index . . . . . . . . . . . . . . . 499
UPDCNTL—Update Control . . . . . . . 481
UPDMVS8—Update MVS Sequenced 8 . . . . 485
Figures ix
249. UPDSEQ0 Update Data Set . . . . . . . 490 251. UPDSUMO Data Set Using Word Compare 492
250. UPDSUMO Data Set Using Line Compare 491 252. UPDSUMO Data Set Using Byte Compare 493
The first part provides information about using ISPF options 0–10.
Chapter 2, “Settings (Option 0),” describes the ISPF Settings panel and related
pop-up windows.
Chapter 3, “View (Option 1),” describes how Browse (Option 1) allows you to
display source data and listings stored in ISPF libraries or other partitioned or
sequential data sets.
Chapter 4, “Edit (Option 2),” describes how Edit (Option 2) allows you to create,
display, and change data stored in ISPF libraries or other partitioned or sequential
data sets.
Chapter 5, “Utilities (Option 3),” describes the different functions for library, data
set, and catalog maintenance.
Chapter 7, “Batch (Option 5),” describes how Batch (Option 5) allows ISPF to run
the batch processors.
Chapter 8, “Command (Option 6),” describes Command (Option 6), and how ISPF
allows you to enter TSO commands, CLISTs, and REXX EXECs on the Command
line of any panel and in the Line Command field on data set list displays.
Chapter 10, “IBM Products (Option 9),” describes the other IBM products that are
supported as ISPF dialogs.
Chapter 11, “SCLM (Option 10),” provides an overview of the SCLM product.
Chapter 12, “ISPF Object/Action Workplace (Option 11),” describes the Workplace
option (Option 11).
Appendix B, “SuperC Listings,” describes and explains the kinds of listings you
can produce using SuperC.
You can use LookAt from the following locations to find IBM message
explanations for z/OS® elements and features, z/VM®, VSE/ESA™, and Clusters
for AIX® and Linux:
v The Internet. You can access IBM message explanations directly from the LookAt
Web site at http://www.ibm.com/eserver/zseries/zos/bkserv/lookat/.
v Your z/OS TSO/E host system. You can install code on your z/OS or z/OS.e
systems to access IBM message explanations, using LookAt from a TSO/E
command line (for example, TSO/E prompt, ISPF, or z/OS UNIX® System
Services running OMVS).
v Your Microsoft® Windows® workstation. You can install code to access IBM
message explanations on the z/OS Collection (SK3T-4269), using LookAt from a
Microsoft Windows command prompt (also known as the DOS command line).
v Your wireless handheld device. You can use the LookAt Mobile Edition with a
handheld device that has wireless access and an Internet browser (for example,
Internet Explorer for Pocket PCs, Blazer, or Eudora for Palm OS, or Opera for
Linux handheld devices). Link to the LookAt Mobile Edition from the LookAt
Web site.
You can obtain code to install LookAt on your host system or Microsoft Windows
workstation from a disk on your z/OS Collection (SK3T-4269), or from the LookAt
Web site (click Download, and select the platform, release, collection, and location
that suit your needs). More information is available in the LOOKAT.ME files
available during the download process.
The ZOS390RL variable contains the level of the z/OS release running on your
system.
The ZISPFOS system variable contains the level of ISPF that is running as part of
the operating system release on your system. This might or might not match
ZOS390RL. For this release of ISPF, the variable contains ISPF for z/OS 01.06.00.
When migrating from one version of ISPF to another, you must reassemble and
relink the SCLM project definition.
Note
This book contains terminology, maintenance, and editorial changes. Technical
changes or additions to the text and illustrations are indicated by a vertical
line to the left of the change.
Starting with z/OS V1R2, you may notice changes in the style and structure
of some content in this book—for example, headings that use uppercase for
the first letter of initial words only, and procedures that have a different look
and format. The changes are ongoing improvements to the consistency and
retrievability of information in our books.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
2 You can use Edit to create or change source data, such as program code
and documentation, using the ISPF full-screen editor. You can scroll the
data up, down, left, or right. You can change the data by using Edit line
commands, which are entered directly on a line number, and primary
commands, which are entered on the command line. See Chapter 3, “View
(Option 1)” and refer to ISPF Edit and Edit Macros for more information.
3 Utilities perform library and data set maintenance tasks, such as moving
or copying library or data set members, displaying or printing data set
names and volume table of contents (VTOC) information, comparing data
sets, and searching for strings of data. See Chapter 5, “Utilities (Option 3)”
for more information.
4 Foreground calls IBM language processing programs in the foreground.
See Chapter 6, “Foreground (Option 4)” for more information.
5 Batch calls IBM language processing programs as batch jobs. ISPF
generates Job Control Language (JCL) based on information you enter and
submits the job for processing. See Chapter 7, “Batch (Option 5)” for more
information.
6 Command calls TSO commands, CLISTs, or REXX EXECs under ISPF. See
Chapter 8, “Command (Option 6)” for more information.
7 Dialog Test tests individual ISPF dialog components, such as panels,
messages, and dialog functions (programs, commands, menus). See
Chapter 9, “Dialog Test (Option 7)” for more information.
9 You can use the IBM Products option to select other installed IBM
program development products on your system. Products supported are:
v Cross System Product/Application Development (CSP/AD)
v Cross System Product/Application Execution (CSP/AE)
v Information/System (INFO/SYS)
v COBOL Structuring Facility foreground dialog (COBOL/SF-F)
v COBOL Structuring Facility background dialog (COBOL/SF-B)
v Screen Definition Facility II (SDF II) licensed program
v Screen Definition Facility II-P (SDF II-P) licensed program.
See Chapter 10, “IBM Products (Option 9)” for more information.
10 SCLM controls, maintains, and tracks all of the software components of an
application. See Chapter 11, “SCLM (Option 10)” and refer to ISPF Software
Configuration and Library Manager (SCLM) Developer’s and Project Manager’s
Guide for more information.
11 Workplace gives you access to the ISPF Workplace, which combines many
of the ISPF functions onto one object-action panel. See Chapter 12, “ISPF
Object/Action Workplace (Option 11)” for more information.
X EXIT leaves ISPF using the log and list defaults. You can change these
defaults from the Log/List pull-down on the ISPF Settings panel action
bar.
See “Status Area on the Primary Option Menu” on page 9 for more
information about using these choices to tailor the status area.
Help The Help pull-down offers you the following choices:
1 General
2 Settings
3 View
4 Edit
5 Utilities
6 Foreground
7 Batch
8 Command
9 Dialog Test
10 LM Facility
11 IBM Products
12 SCLM
13 Workplace
14 Exit
15 Status Area
16 About...
17 Changes for this Release
18 Tutorial
19 Appendices
20 Index
Note: The ISPF Status panel also contains an action bar choice called ″Status″.
This does not affect which Status option displays on the Primary Option
Menu panel. It determines which Status option displays within the ISPF
Status panel.
The first five logical screens, created by a SPLIT or related command, each have
their own status view. For each screen after that, the view defaults to the setting of
the first screen.
Status Pull-Down
When you select one of the choices in the Status pull-down on the ISPF Primary
Option Menu action bar (shown in Figure 2), you specify what you want to display
in the status area on the Primary Option Menu panel.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Note: The current setting is shown as an unavailable choice; that is, displays in
blue (the default) with an asterisk as the first digit of the selection number.
If you are running in GUI mode the choice is grayed.
Session
The Session view, shown in Figure 3, displays the following information in the
status area:
v User ID
v Time
v Terminal
v Screen
v Language
v Application ID
v TSO logon
v TSO prefix
v System ID
v MVS account
v Release.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
SYSNODE
The network node name of your installation’s JES.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Release
Displays the following variables:
v ZOS390RL— The z/OS Release running on your system.
v ZISPFOS— The level of ISPF code that is running as part of z/OS on
your system. This might or might not match ZOS390RL.
v ZENVIR— The ISPF Environment description. Refer to the table of
system variables in the ISPF Dialog Developer’s Guide and Reference for a
complete explanation.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Function Keys
The Function Keys view, shown in Figure 6 on page 13, displays the following
information in the status area:
v Number of keys
v Keys displayed per line
v Primary range (lower or upper)
v Display set (primary or alternate)
v List name (name of the currently active keylist)
v List applid (application ID for the currently active keylist)
v List type (private or shared)
v Keylists (on or off).
Note: See “Working with Function Keys and Keylists (The Function Keys Action
Bar Choice)” on page 41 for information about changing these settings.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Figure 6. ISPF Primary Option Menu Status Area – Function Keys View
Calendar
The Calendar view, shown in Figure 7, displays the calendar for the current month
in the status area.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
All of the fields on the calendar are point-and-shoot fields that function as follows:
If you select ISPF displays
< the previous month.
calendar the current month.
> the next month.
Month, e.g. July
the Calendar Month pop-up. Allows you to specify the month. See
“Customizing the Calendar” on page 19 for details.
Year, e.g. 2003 the Calendar Year pop-up. Allows you to specify the year. See
“Customizing the Calendar” on page 19 for details.
Day the Calendar Start Day pop-up. Allows you to specify Saturday,
Sunday, or Monday as the start day for the calendar. See
“Customizing the Calendar” on page 19 for details.
Date the Julian Date pop-up. Provides the Julian date for the date
selected.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Time the Calendar Time Format pop-up. Allows you to specify a 12-hour
or 24-hour time format for the calendar. See “Customizing the
Calendar” on page 19 for details.
Day of year the Standard Date pop-up. Provides the standard date for the day
specified in the popup (defaults to the date selected in the
calendar).
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
User Status
The User Status view, shown in Figure 10, displays the status information that you
have defined in the Status Area panel.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Figure 10. ISPF Primary Option Menu Status Area – User Status View
Note: If you are running in GUI mode, this function will be displayed as a push
button.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Figure 11. ISPF Primary Option Menu Status Area – User Point-And-Shoot View
None
If you select None from the Status pull-down, nothing will be displayed in the
status area.
Note: Changing the status area viewed in this panel will not affect the choice
selected on the ISPF Primary Option Menu panel.
Status The Status pull-down, shown in Figure 13 on page 18, offers you
the following choices:
1 Session
2 Function keys
3 Calendar
4 User status
5 User point and shoot
6 None
Options The Options pull-down, shown in Figure 14 on page 19, offers you
the following choices:
1 Calendar start day... Displays the Calendar Start Day
pop-up, where you can specify Saturday, Sunday, or Monday
as the start day for the calendar.
2 Calendar colors... Displays the Calendar Colors pop-up,
where you can change the colors on the calendar.
3 User status customization... Displays the User View
Customization pop-up, where you can define what you want
displayed in the status area.
4 User point and shoot customization... Displays the User
Point and Shoot Customization pop-up, where you can define
point-and-shoot fields to be displayed in the status area.
Changing the month display: You can change the month that displays in the
calendar in a number of ways:
v Click the < or > symbols to display the previous or next month.
v Click the Calendar point-and-shoot field to display the current month.
v Set the month display to a particular month by selecting the month name
point-and-shoot field and entering a number in the Calendar Month pop-up
window:
Changing the year display: You can change the year that displays in the calendar
by selecting the year point-and-shoot field and entering the required year (between
1801 and 2099) in the Calendar Year pop-up window.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Changing the starting day: You can change the calendar display so that the
weeks begin on a Saturday, Sunday or Monday. To do this:
1. Select any day name point-and-shoot field (e.g. Mo or Tu).
OR
2. From the ISPF Status action bar, choose Options and then 1. Calendar start
day... The Calendar Start Day pop-up is displayed.
3. Enter option 1. Sunday, 2. Monday or 3. Saturday.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Changing the time format: You can change the time format to a 12 or 24 hour
clock. To do this, select the Time point-and-shoot field and enter option 1 or 2 in
the Calendar Time Format pop-up window.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
2. Enter a heading in the Description field and the name of a System variable or
site-defined variable in the Variable name field. See the ISPF Dialog Developer’s
Guide and Reference for a list of System Variable names.
3. Press EXIT (F3) or END to exit and save the changes. Press CANCEL (F12) to
exit without saving the changes.
2. Enter the text to appear in the status area, in the field on the left of the panel.
3. Enter the Service parameters to be invoked in the lines on the right of the
panel. Refer to ISPF Services Guide for information about these parameters.
4. Press EXIT (F3) or END to exit and save the changes. Press CANCEL (F12) to
exit without saving the changes.
This chapter explains how to use the fields on the ISPF Settings panel and the
action bar choices. Some of the things you can specify are:
v Terminal characteristics
v Default options for processing the ISPF list and log data sets
v Function key assignments
v Placement of command lines
v List data set characteristics
v GDDM® graphic print parameters
v Keylist modifications
v Dialog Test option
v Default colors
v Values of CUA panel elements
v Point-and-shoot color and highlight changes
v ENVIRON command options.
This facility can be started from any command line with the SETTINGS command,
from the Settings choice on the Menu pull-down on any action bar where it is
available, or by selecting option 0 on the ISPF Primary Option Menu. Typically, the
Settings facility should be included as an option on an application’s primary
option menu or as a choice on a pull-down on an application’s primary option
menu.
If you select option 0 on the ISPF Primary Option Menu, the panel shown in
Figure 22 is displayed.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Select Options
Use a slash to select the following options:
v Command line at bottom
v Panel display CUA mode
v Long message in pop-up
v Tab to action bar choices
v Tab to point-and-shoot fields
v Restore TEST/TRACE options
v Session Manager mode
v Jump from leader dots
v Edit PRINTDS Command
v Always show split line
Blank out the slash to deselect an option; each option is described below.
Command line at bottom
Specifies that the command line is to appear at the bottom of each logical
screen. If you have specified that the panel should be displayed in CUA
mode, the command line placement defaults to the bottom.
Notes:
1. The default is to have the command line placement at the bottom.
However, if your current application profile table specifies ASIS, the
default does not override it.
2. If you deselect this field, the command line appears as specified in the
panel definition statements. Unless indicated in the panel definition, it
appears at the top of the panel.
When you select the Command line at bottom option, the following
changes take place:
v The command line moves to the last line of the logical screen or the line
above the function keys depending on the CUA mode setting (see
Table 1 on page 28).
v Each line that follows the command line shifts up one line.
v The long message overlays the line above the new command line
location.
If the command line for a table display panel has been moved to the
bottom and if no alternate placement has been specified for the long
message line, the line directly above the repositioned command line is
reserved (left blank) for the display of long messages. Otherwise, if you
enter erroneous data on that line, a long message could overlay that
data.
v In general, the display location of the function key definitions depends
on several variables.
– If the panel display mode CUA option is not selected, and the
KEYLIST option is set to OFF, the function key definitions display on
the lines immediately above the long message line.
– If the panel display mode CUA option is on, and the KEYLIST option
is set to OFF, the function key definitions display below the long
message line.
– If the KEYLIST option is set to ON, and the panel definition does not
contain a )PANEL statement, the positioning of the function keys
depends on the CUA mode setting.
– If the KEYLIST option is set to ON, and the panel definition contains
a )PANEL statement, the positioning of the function keys is below the
long message line.
If the Panel display CUA mode option is not selected, an exception to
this situation occurs when an alternate placement for the long message
line has been specified using the LMSG keyword on the )BODY header
statement. Under these circumstances, the function key definitions
display immediately above the command line.
Note: You cannot use the Tab key for this purpose if you are running in
GUI mode.
Tab to point-and-shoot fields
Specifies that you want to use the Tab key to move the cursor through the
point-and-shoot fields on a panel.
Note: You cannot use the Tab key for this purpose if you are running in
GUI mode.
Restore TEST/TRACE options
When you select Dialog Test facility (option 7), certain TEST and TRACE
options are established that can be different than those specified during
ISPF start up. If you select Restore TEST/TRACE options, the TEST or
TRACE values are restored to the ISPF call values when you exit dialog
test. If you deselect the field, the TEST or TRACE values are not restored
when you exit dialog test.
For more information about dialog test, see Chapter 9, “Dialog Test (Option
7).”
Session Manager mode
Enter a slash to indicate that the Session Manager should handle any line
mode output from the processing program.
Jump from leader dots
Enter a slash to enable the ISPF jump function from field prompts that
have leader dots ( . . or ... ). Field prompts that have the ==> will always
have the jump function enabled.
If the application developer defines the NOJUMP(ON) attribute keyword
on a specific input field, this disables the ″Jump from leader dots″ and
takes precedence over the selected Settings ″Jump from leader dots″ or the
configuration table setting of ″YES″ for ″Jump from leader dots″.
Edit PRINTDS Command
Enter a slash to intercept the local print request to allow you to modify the
statement before the PRINTDS command begins. For more information on
editing the PRINTDS command, see the Libraries and Data Sets chapter of
ISPF User’s Guide Volume I.
Always show split line
Specifies that the split line in split screen mode, as seen on a 3270 display,
should always be shown. The default for this option is that the option is
selected. By deselecting this option, the split line does not display when
the screen is split at the top or the bottom of the screen.
Enable EURO Sign
Enter a slash to enable the EURO sign (currency symbol). Your terminal or
emulator must support the EURO sign for this option to work.
Scroll member list
Enter a slash to specify that ISPF should scroll to the first member selected
in the member list after processing. If the Option field is deselected,
automatic member list scrolling is disabled and the cursor is placed in
front of the last member selected.
Terminal Characteristics
The Terminal Characteristics portion of the ISPF Settings panel allows you to
specify values for the screen format and terminal type. Each of these characteristics
is described below.
Screen format
Specification of screen format applies only to 327x and 3290 terminals (or a
terminal emulator set to a mode that emulates a 327x or 3290 terminal).
ISPF ignores screen format for other types of terminal.
Data Format is based on data width.
Std Format is always 24 x 80 characters.
Max Format is determined by the maximum data width and height of
the terminal or emulator.
Part Format uses hardware partitions (3279 only)
Notes:
1. ISPF supports screen sizes from 24 x 80 characters to 62 x 160
characters.
2. If you are in an Edit session or you are using the EDIT service, ISPF
will not allow you to change the screen format.
Terminal type
Specify a valid terminal type. If you are using a terminal emulator, select
the type of terminal that is being emulated (more than likely, a 3278 or
3278x).
Specification of a terminal type allows ISPF to recognize valid (displayable)
characters. You should keep in mind that the terminal type value that you
specify to ISPF might not be the actual terminal type. For example, if your
terminal is a 3279, you specify 3278 because a 3279 terminal has the same
character set as a 3278. The keyboard character sets for the specified
terminal and the actual terminal are always compatible.
The terminal type designations in the text of this document are often the
value to be specified to ISPF rather than the actual terminal type.
For a list of ISPF-supported terminal types, refer to ISPF Planning and
Customizing. For specific information about the type value to specify to
ISPF for each supported terminal, start Help from the ISPF Settings panel.
You can also select a terminal type by using the ISPTTDEF program, as
described in ISPF Dialog Developer’s Guide and Reference.
This panel can also include one or more installation-dependent options for
terminal type, for example:
3277KN 3277 Katakana terminals
3278CF 3278 Canadian French terminals
3278KN 3278 Katakana terminals.
A 5550-3270 Kanji emulation Version 3 terminal has the same character set
as a 3278 Katakana terminal, so you should specify 3278KN as the terminal
type. Also, because the 5550 running with the Japanese 3270PC/G Version
3 or 3270 PC Version 5 has the same character set as a 3278 Katakana
terminal, in either case you should specify 3278KN as the terminal type.
Figure 25 shows how the graphic in Figure 23 would appear if the PRINTG
command were issued with an aspect ratio of 1.
General
The General portion of the ISPF Settings panel allows you to specify values for the
input field pad and command delimiter.
Input field pad
Specifies a pad character that controls the initial padding of blank
(unfilled) panel input fields, including the selection panels, but not the
data portion, of an Edit display. Within Edit, you control null or blank
padding with Edit commands.
The pad character specified can be a B (blank), N (nulls), or any special
(non-alphanumeric) character.
Note: When you are running in GUI mode, blank pad characters will be
displayed as nulls in order to avoid the need to delete blank
characters when replace mode is not available.
Command delimiter
You can stack commands on the command line by separating them with a
delimiter. The default delimiter, the semicolon, can be changed using this
option. Alphanumeric characters, the period (.), and the equal sign (=) are
not valid command delimiters. Stacking allows you to enter, for example:
===> FIND DEPT;HEX ON
which finds the characters DEPT and then displays the file at that point in
hexadecimal mode.
The system variable for the delimiter is ZDEL. For more information about
ZDEL, refer to the ISPF Dialog Developer’s Guide and Reference.
Log/List
The Log/List pull-down offers you the following choices (see “Specifying
Log and List Defaults and Characteristics (The Log/List Action Bar Choice)”
on page 35 for more information):
1 Log Data set defaults. Displays the Log Data Set Defaults panel.
2 List Data set defaults. Displays the List Data Set Defaults panel.
3 List Data set characteristics. Displays the List Data Set Characteristics
panel.
4 JCL... Displays the Log and List JCL pop-up.
Function keys
The Function keys pull-down offers you the following choices (see “Working
with Function Keys and Keylists (The Function Keys Action Bar Choice)” on
page 41 for more information):
1 Non-Keylist PF Key settings. Displays the PF Key Definitions and
Labels panel.
2 Keylist settings... Displays the Keylist Utility for ISP pop-up.
3 Tailor function key display. Displays the Tailor Function Key
Definition Display panel.
4 Show all function keys. Changes the function key display. This will be
an unavailable choice if you are currently showing all function keys.
5 Show partial function keys. Changes the function key display. This
will be an unavailable choice if you are currently showing a partial list
of function keys.
6 Remove function key display. Removes function keys from your
screen. This will be an unavailable choice if you are currently not
showing function keys.
7 Use private and shared. Equivalent to using the KEYLIST PRIVATE
command.
8 Use only shared. Equivalent to using the KEYLIST SHARED command.
9 Disable keylists. Disables keylists. This choice is not available if you
are currently running with keylists disabled.
10 Enable keylists. Enables keylists. This choice is not available if you are
currently running with keylists enabled.
Colors
The Colors pull-down offers you the following choices (see “Changing
Default Colors (The Colors Action Bar Choice)” on page 57 for more
information):
1 Global colors... Displays the Global Color Change Utility panel.
2 CUA Attributes... Displays the CUA Attribute Change Utility panel.
3 Point-and-Shoot... Displays the CUA Attribute Change Utility panel,
positioned on the Point-and-Shoot panel element.
Environ
The Environ pull-down offers you the following choices (see “Specifying ISPF
ENVIRON Settings (The Environ Action Bar Choice)” on page 64 for more
information):
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===>
F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE
F7=UP F8=DOWN F9=SWAP F10=LEFT F11=RIGHT F12=RETRIEVE
Figure 26. Log/List Pull-Down on the ISPF Settings Panel Action Bar (ISPISMMN)
The defaults can also be used when you issue the LOG or LIST command. You
may specify the characteristics of the records to be contained in the list data set
when it is defined.
Lines per page can range from 1–999. ISPF uses this value to determine
when to cause a page eject if the eject control is not provided by the
dialog; for example, when the dialog issues a LIST service request without
the CC keyword specified.
Primary/Secondary pages
Primary/secondary allocation parameters are specified in terms of the
anticipated number of pages of printout. These values are automatically
converted by ISPF to the appropriate number of blocks before allocating
space for the log data set.
If you modify the primary/secondary allocation parameters after the data
set has been allocated, the new values take effect the next time you start
ISPF. The log data set is allocated the first time you perform some action
that results in a log message, such as saving edited data or submitting a
batch job.
If you request default processing options for the log data set, the following rules
apply:
v If you specify Print data set and delete (1), you must also specify a Batch
SYSOUT class and job statement information. If you specify Print data set and
delete for both log and list, you can specify different Batch SYSOUT classes, but
only one job is submitted for printing both data sets.
v If you specify routing to a local printer, you must specify a Local printer ID or
writer name, and Batch SYSOUT must be blank. You can also enter a Local
SYSOUT class if one is defined.
If you do not follow these rules or do not specify default processing options,
primary option X or the RETURN command causes the final termination panel to
be displayed.
Local printer ID
Enter the name that your installation has assigned to an IBM 328x type of
printer or the name of the external writer program. The default is blank. If
you enter a name in this field, be sure to leave the Batch SYSOUT class
field empty.
Lines per page
Normal values for lines per page are:
60 When printing 6 lines per inch
80 When printing 8 lines per inch.
Lines per page can range from 1–999. ISPF uses this value to determine
when to cause a page eject if the eject control is not provided by the
dialog; for example, when the dialog issues a LIST service request without
the CC keyword specified.
Primary/Secondary pages
Primary/secondary allocation parameters are specified in terms of the
anticipated number of pages of printout. These values are automatically
converted by ISPF to the appropriate number of blocks before allocating
space for the list data set.
If you modify the primary/secondary allocation parameters after the data
set has been allocated, the new values take effect the next time you enter
ISPF. The list data set is allocated the first time you request a print function
or a dialog issues a LIST service request.
If you request default processing options for the list data set, the following rules
apply:
v If you specify Print data set and delete (1), you must also specify a Batch
SYSOUT class and job statement information. If you specify Print data set and
delete for both log and list, you can specify different Batch SYSOUT classes, but
only one job is submitted for printing both data sets.
v If you specify routing to a local printer, you must specify a Local printer ID or
writer name, and Batch SYSOUT must be blank.
If you do not follow these rules or do not specify default processing options,
primary option X or the RETURN command causes the final termination panel to
be displayed.
After reviewing or changing the parameters on this panel, enter the END
command to return to the previous menu.
Specifications for logical record length and line length values can affect truncation
of lines written to the list data set by a LIST service request. See the description of
the LIST service in ISPF Services Guide for more information.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===> LISTDSC
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
The first page of output would contain the first 130 bytes of the panel.
The second page would contain the last 30 bytes. This technique is
referred to as the cut and paste method of printing.
v If a panel to be printed is 132 bytes wide and the printer supports this
line length, you should specify:
RECFM FBA or VBA
Line Length 132
LRECL 133 (allows for one ANSI-defined control character).
The entire panel would be printed on one page of output.
v If a panel to be printed is 80 bytes wide, ISPF uses the default values for
the LIST parameters. The entire panel would be printed on one page of
output.
JCL
When you select JCL... from the Log/List pull-down on the ISPF Settings panel
action bar, the pop-up shown in Figure 30 is displayed to allow you to specify up
to four default job statements to be used for printing a log or list data set.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===> LLJCL
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Nearly all panels in ISPF have associated keylists, although specific keylists
typically serve numerous panels. There are several keylists used in the ISPF
product panels. These keylists all start with the characters ISR. In addition, ISPF
contains some keylists that start with the characters ISP. They are not used in any
ISPF product panels, but can be used by an application if needed. Keylists are used
when an application panel contains a )PANEL statement.
To accommodate both users who require CUA-compliant keylists and those who
prefer to use the traditional ISPF function key assignments, F1–F12 are assigned
CUA-compliant values, and F13–F24 are assigned traditional ISPF values.
Therefore, the user who runs in default mode (ZPRIKEYS set to UPP; also see
“Tailor Function Key Definition Display” on page 54) can retain the traditional key
settings.
Note: Function keys in Edit are documented in ISPF Edit and Edit Macros. They are
not CUA-compliant.
The KEYS and KEYLIST commands have been modified to benefit the user as well.
When KEYS is issued from a panel that is not using a keylist, the PF Key
Definitions and Labels panel is displayed, which allows you to change the ZPF
variable settings, as in previous versions of ISPF. However, if the keys command is
issued from a panel with an active keylist, the associated Keylist Utility panel
Change panel is displayed.
The user can also control the use of keylists associated with panels using the
KEYLIST command. Specifying KEYLIST OFF causes ISPF to ignore the keylist in
all logical screens running under the application ID from which the KEYLIST OFF
command was issued, and to use the ZPF variables for controlling function keys.
The KEYLIST ON command (the default) causes ISPF to recognize the preeminence
of keylists again. KEYLIST ON and OFF are equivalent to the Enable and Disable
keylist choices on the Function keys pull-downs discussed in “Keylist Settings” on
page 46.
F1 HELP Short
F2 SPLIT Long
F3 EXIT Short
F9 SWAP Long
F12 CANCEL Short
F13 HELP Short
F14 SPLIT Long
F15 EXIT Short
F21 SWAP Long
F24 CANCEL Short
F1 HELP Short
F2 SPLIT Long
F3 EXIT Short
F5 EXHELP Short
F6 KEYSHELP Short
F7 UP Long
F8 DOWN Long
F9 SWAP Long
F10 LEFT Long
F11 RIGHT Long
F12 CANCEL Short
Figure 31 shows the Function keys pull-down on the ISPF Settings panel action bar.
Each pull-down choice is described following the panel.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Figure 31. Function Keys Pull-Down on the ISPF Settings Panel Action Bar (ISPISMMN)
If you define your application panels using panel definition statements, use the PF
Key Definitions and Labels - Primary Keys panel shown in Figure 32 to assign
function keys and associated labels to ISPF commands.
Note: See “Keylist Settings” on page 46 to find out how to assign function keys
that are associated with a keylist.
PF1 . . . HELP
PF2 . . . SPLIT
PF3 . . . END
PF4 . . . RETURN
PF5 . . . RFIND
PF6 . . . RCHANGE
PF7 . . . UP
PF8 . . . DOWN
PF9 . . . SWAP
PF10 . . LEFT
PF11 . . RIGHT
PF12 . . RETRIEVE
Press ENTER key to display alternate keys. Enter END command to exit.
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F12=Cancel
Note: The panel in Figure 32 is displayed for terminals with 12 function keys. For
terminals with 24 function keys, the first panel displayed shows the primary
keys (F1–F12). When you press the Enter key, ISPF displays a panel showing
the alternate keys (F13–F24). To alternate between the two panels, press the
Enter key.
You can assign function keys to system commands, such as HELP or END, to
commands that are meaningful within a particular function or environment, such
as the Edit FIND and CHANGE commands, and to line commands, such as the
Edit or dialog test I or D commands.
Before changing function key assignments, verify the terminal type selected on the
ISPF settings panel and the number of function keys (12 or 24). For a list of valid
terminal types refer to Table 3 on page 31.
You can define or change a function key function simply by equating the key to a
command. For example:
PF9 . . . CHANGE ALL ABC XYZ
PF12 . . PRINT
In the example, F9 has been equated to an Edit command, and F12 has been
equated to the system-defined PRINT command.
If you enter a blank for any function key definition, the key is restored to its ISPF
default.
A function key definition beginning with a colon (:) is treated as a special case. The
colon is stripped off, and the command to which the key is equated is inserted in
the first input field on the line at which the cursor is currently positioned.
A function key definition beginning with a greater-than sign (>) is another special
case. It causes the command to be passed to the dialog, regardless of whether the
command appears in the command tables. This feature provides compatibility with
SPF, in which Edit and Browse commands were defined with a greater-than sign.
When an ISPF function is executing, do not press the RESET key and then attempt
to enter information or use a function key, because the results are unpredictable.
The label fields shown in Figure 32 on page 44 allow you to specify user-defined
labels for the displayed representations of function key definitions. This provides
for displaying meaningful words of eight characters or fewer, rather than the first
eight, possibly meaningless, characters of a lengthy function key definition.
If a label is not assigned, the definitions displayed for that function key consist of
the first eight characters of the function key definition.
If the label value is BLANK, the function key number and the equal sign display,
but the value portion of that function key definition displays as actual blanks. This
label might be used if, for example, a function key is not defined or if it is
meaningless to the user, but the dialog developer wants each function key number
to appear sequentially in the function key definition lines.
No function key information, not even the number, appears if the label value for
that key is NOSHOW.
Figure 33 on page 46 shows how the function key panel can be used to assign
definitions and labels. In this example, F4 has been equated to a TSO data
management command, while F12 has been equated to a command that requests
job submission. Labels for several function keys are defined as well.
PF1 . . . HELP
PF2 . . . SPLIT
PF3 . . . END
PF4 . . . TSO LISTALC ST
PF5 . . . RFIND
PF6 . . . RCHANGE
PF7 . . . UP
PF8 . . . DOWN
PF9 . . . SWAP
PF10 . . LEFT
PF11 . . RIGHT
PF12 . . TSO SUBMIT NOTIFY
Press ENTER key to display alternate keys. Enter END command to exit.
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F12=Cancel
Figure 33. Using the PF Key Definitions and Labels Panel (ISPOPT3E)
Figure 34 shows the function key settings that are displayed on a panel when
defined using the key definitions and labels in Figure 33.
Keylist Settings
To create or change a keylist associated with your panels, or to refer to or delete a
keylist help panel from your keylist, select the Keylist settings... choice from the
Function keys pull-down on the ISPF Settings panel action bar, or enter the
KEYLIST command. The first panel displayed is similar to Figure 35. If you Enter
the KEYS command from a panel that uses a keylist, the keylist change panel for
the keylist active on the original panel is displayed.
The application ID is shown on the title line of the panel (ISR in Figure 35) and
defaults to the application ID of the keys table in which the keylist was found
when the KEYLIST command was entered. You can specify the keylist application
ID on the )PANEL statement, or, if using DTL, it can be specified when you call
the ISPF conversion utility using the KEYLAPPL option on the ISPDTLC
command. If the panel does not specify an application ID, ISPF searches the
currently executing application’s keys table for a keylist that has the same name as
the name specified on the PANEL tag. If the keylist is not found, and the current
application ID is not ISP, ISPF searches the ISP application.
The column marked Type indicates whether a keylist is shared or is a private copy.
For information about the KEYLIST SHARED and KEYLIST PRIVATE system
commands, see the chapter on Using Commands, Function Keys, and Light Pen or
Cursor Selection in the ISPF User’s Guide Volume I. Shared keylists are created by
the ISPF DTL Conversion Utility. They cannot be deleted by the keylist utility. If a
shared keylist is modified by the keylist utility, it is saved as a private keylist copy
in a table named xxxxPROF, where xxxx is the application ID. The keylist utility
now shows the keylist as a private copy. If you have issued the KEYLIST SHARED
command, you can still modify a keylist, but you cannot see the changes reflected
in the function keys until the KEYLIST PRIVATE command is issued.
Note: The keylist utility is meant for users to modify function keys for their own
use. To define function keys for all users of an application or for site-wide
use, the definitions in the Dialog Tag Language should be modified and a
new xxxxKEYS table should be generated.
Figure 36. Keylist Utility with File Action Bar Pull-Down (ISPKLUP)
To remove a help panel name from a keylist, replace the help panel
name with blanks.
Definition
If a display format or a label is specified, a definition must also be
specified. Any definition is valid.
Format
The only valid display formats are:
LONG The default. Indicates that the key label should be
displayed in the function key area when the FKA
command is toggled to the first cycle after OFF.
SHORT Indicates that the key label should be displayed in
the function key area when the FKA command is
toggled to the first or second cycle after OFF. A key
will display more often in the function key area if
it is given the SHORT display format.
NO Indicates that the key label should never be
displayed in the function key area, regardless of
the FKA command toggle cycle.
Label Any label is valid. If the Label field is left blank, it will default to
the definition. This will happen only if the field is blank. If the
Label field is not blank and the definition is changed, the Label
field will not change automatically.
View To view a keylist, but not modify it, enter the keylist name when
prompted. Select the keylist with a slash, then select View from the File
pull-down, or type V next to the keylist name displayed and press Enter.
The screen shown in Figure 39 on page 52 is displayed.
If you select View, the help panel name, key definitions, display formats,
and labels are displayed but cannot be changed.
Delete To delete a private copy of a keylist, enter the keylist name when
prompted. Select the keylist with a slash, then select Delete from the File
pull-down, or type D next to the keylist name displayed and press Enter.
The Delete Keylist Confirmation pop-up shown in Figure 40 on page 53 is
displayed.
Note: Shared keylists can only be deleted using the Dialog Tag Language.
Figure 40. Keylist Utility with Delete Keylist Confirmation Pop-Up (ISPKLUP)
View Pull-Down: To display another set of keys on the Keylist Utility panel,
select View on the action bar. An example of the View pull-down is shown in
Figure 41 on page 54.
Figure 41. Keylist Utility with View Action Bar Pull-Down (ISPKLUP)
From the Tailor Function Key Definition Display panel you can set the following
function key parameters:
Number of keys
The number of function keys you specify controls the particular set of
function key definitions currently in use.
ISPF automatically determines the terminal type, screen size, and number
of function keys:
v If the screen size is greater than 24 lines, but the terminal type specified
implies a maximum of 24 screen lines, ISPF sets the terminal type to
3278.
v If you press a function key higher than 12, but the value specified for
the number of function keys on your terminal is 12, ISPF sets the
terminal type to 3278 and the number of function keys to 24.
ISPF cannot determine the terminal type or number of function keys in the
following cases:
v If you switched between a 3277 and 3278 Model 2, both of which are
24-line terminals
v If you switched from a terminal with 24 function keys to a terminal with
12 function keys.
In these cases, you must inform ISPF of the terminal type and number of
function keys you are using. Otherwise, ISPF uses an incorrect character
set and invalid function key definitions.
v If you specify 3278, ISPF initializes the number of keys to whatever was
stored from the user’s last ISPF session. If no number is stored from a
prior session, the number of keys is initialized to 12.
v If you press a function key higher than 12, ISPF sets the number of keys
to 24. ISPF cannot set the number of keys to 24 for the 3278T terminal.
Keys per line
You can specify the number of keys per line to be displayed on the
function key definition lines. Six or Maximum possible can be specified,
indicating either six keys or the maximum possible keys. Six ensures
consistency across all panels. Maximum possible can save space on
crowded panels. The Maximum possible option is forced when you select
the Panel display CUA mode option on the ISPF Settings panel.
Primary range
You can specify that the primary key range be:
Lower Primary keys are F1–F12.
Upper Primary Keys are F13–F24.
Choosing Keylist settings... from the pull-down is like using the KEYLIST
command, and the Tailor Function Key Display choice calls up the Tailor Function
Key Definition Display panel.
Each of these pull-down choices has an equivalent PFSHOW and FKA command
associated with it. The commands operate as toggles; the pull-down choices
become unavailable if they are the current setting.
Table 9 on page 57 explains the relationship between the pull-down choices and
their related command combinations.
Figure 43 on page 58 shows the Colors pull-down on the ISPF Settings panel action
bar. Each pull-down choice is described following the panel.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Figure 43. Colors Pull-Down on the ISPF Settings Panel Action Bar (ISPISMMN)
Global Colors
For ISPF-supported seven-color terminals, ISPF provides the Global Color Change
Utility (on the host) and the Global GUI Color Change Utility (on the workstation)
to allow you to globally change the current colors ISPF uses for display.
To invoke the utility appropriate for your environment, do one of the following:
v Select the Global colors... choice from the Colors pull-down.
v Issue the ISPF system command COLOR from any ISPF command line.
ISPF displays the Global Color Change Utility panel shown in Figure 44 on page 59
if you are running in host mode; it displays the Global GUI Color Change Utility
panel shown in Figure 45 on page 60 if you are running in GUI mode.
Global Color Change Utility: From the panel shown in Figure 44 on page 59, you
can change the ISPF-defined default colors.
Enter a new value in the color field beside the ISPF-defined default color to be
changed. The following are the valid color choices:
RED
PINK
GREEN
YELLOW
BLUE
TURQ
WHITE.
Note: You can restore the defaults by selecting the Defaults point-and-shoot field
located at the end of the panel command line or by clearing a color field
and pressing Enter.
Color changes are reflected on the panel display immediately after you press Enter.
If you change red to blue by using the ISPF Global Color Change Utility, any panel
element attributes defined as red change to blue on the next display. For example,
if you enter:
RED . . . . . blue____
all panel element attributes with the color red change to blue on the next display.
In the Global Color Change Utility table, if a field is blank and you press Enter, the
ISPF-defined default color is restored.
The EXIT command ends the Global Color Change Utility function and saves
global color changes in the ISPSPROF system profile table. The CANCEL command
ends the Global Color Change Utility function and restores the global color
definitions as they were before the utility was invoked.
Changes to the globally defined colors affect all logical screens whether they are
displayed directly by ISPF or whether ISPF has requested that GDDM perform the
display. Line mode output, fields, and graphics that the dialog has placed on the
screen using direct calls to GDDM are not affected by global color changes.
Field-level help is available for all input fields on the ISPF Global Color Change
Utility panel.
Global GUI Color Change Utility: If you have set up the GUI interface, you can
change its colors. From the Global GUI Color Change Utility panel shown in
Figure 45, you can map each of the seven host colors to one of 16 workstation
colors:
Host Colors Workstation Colors
RED BLACK
PINK DARK BLUE
GREEN DARK GREEN
YELLOW DARK CYAN
BLUE DARK RED
TURQ (turquoise) DARK MAGENTA
WHITE BROWN
LIGHT GRAY
DARK GRAY
LIGHT BLUE
LIGHT GREEN
LIGHT CYAN
LIGHT RED
LIGHT MAGENTA
YELLOW
WHITE
Note: Avoid mapping to colors that are the same color as the panel background
because the data will not be visible. For example, white text on a white
background will not be visible.
1 Host colors for all panel fields. Any colors that you remap affect all panel
fields.
2 Host colors for non-CUA attributes only. Any colors that you remap affect
only panel fields with non-CUA attributes.
3 Workstation default colors for all panel fields. Remapping colors will
have no effect.
The display will reflect any color changes made immediately when you press
Enter.
Note: If a field uses a non-CUA attribute without a color specified, ISPF does not
specify a color for the field and the field defaults to the 3270 default color
on the host. That same field defaults to the workstation default color when
it is displayed on the workstation, even if Host colors for all panel fields is
selected.
Remapping Host Colors: From the Global GUI Color Change Utility panel, select a
drop-down list button corresponding to one of the seven host colors, and ISPF
displays the drop-down list on the panel, as shown in Figure 46.
From the drop-down list, select one of the 16 workstation colors to map to the host
color you selected. For example, if you select the workstation color light magenta
to map to the host color red, any panel element attributes defined as red change to
light magenta on the next display.
The EXIT command terminates the Global GUI Color Change Utility and saves any
global color changes in the ISPSPROF system profile table. The CANCEL command
terminates the Global GUI Color Change Utility and restores the global color
definitions to the values that were in effect before the utility was invoked.
Changes to the globally defined colors affect all logical screens. Background panels
and split screen panels are not immediately affected; the color change does not
occur until the panels are redisplayed.
CUA Attributes
ISPF provides the CUA Attribute Change Utility to allow you to change the default
values of panel colors, intensities, and highlights for panel element attributes. See
the ISPF Dialog Developer’s Guide and Reference for a description of TYPE values for
CUA panel element attributes.
To invoke the ISPF CUA Attribute Change Utility, do one of the following:
v Select the CUA attributes... choice from the Colors pull-down.
v Issue the ISPF system command CUAATTR from any ISPF command line.
The CUA Attribute Change Utility panel shown in Figure 47 is displayed. This is a
scrollable panel that contains the current values for CUA panel element attribute
colors, intensities, and highlights.
You can change the default values by typing over the existing values in the table
with new values. Table 10 on page 62 shows valid change values:
Notes:
1. You can restore the defaults by selecting the Defaults point-and-shoot field
located at the end of the panel command line or by clearing a color field and
pressing Enter.
2. The Active Window Frame panel element, formerly on the Screen Display
Characteristics panel, has been moved to this panel.
Table 10. Valid CUA Attribute Change Values
Color Choices Intensity Choices Highlight Choices
In the CUA Attribute Change Utility table, if a field is left blank and Enter is
pressed, the field defaults to the ISPF provided CUA-defined default value.
Changes made to AB Selected Choice, AB Unselected Choice, Action Message Text,
Function Keys, Informational Message Text, and Warning Message Text take effect
immediately. Changes to other panel elements are reflected in the next panel
display. The values of the panel colors, intensities, and highlights are saved across
ISPF invocations in your ISPF system profile table, ISPSPROF. The changes to the
panel element values affect all logical screens.
The CUA Attribute Change Utility affects only ISPF’s CUA-defined attribute
keywords. For example, the CUA Attribute Change Utility does not override the
following panel element attribute:
% TYPE(OUTPUT) COLOR(RED)
Color changes made using the ISPF Global Color Change Utility override changes
made using the ISPF CUA Attribute Change Utility. For example, you can use the
Global Color Change Utility and change red to blue. You might then use the CUA
Attribute Change Utility and change normal text to red. Normal text will display
as blue.
Field-level help is available for all input fields on the CUA Attribute Change
Utility Panel.
The ISPF-supported CUA-defined default values for the panel element attributes
are listed in ISPF Dialog Developer’s Guide and Reference.
Point-and-Shoot
The Point-and-Shoot panel element on the CUA Attribute Change Utility panel
(shown in Figure 48 on page 64) allows you to adjust the color, intensity and
highlighting of point-and-shoot fields.
See the ISPF User Interface chapter of the ISPF User’s Guide Volume I for
information on the point-and-shoot feature.
Figure 48. CUA Attribute Change Utility Panel Positioned on the Point-and-Shoot Panel
Element (ISPOPT1X)
To change any of the three attributes, type over the existing values. The changes
are reflected on the next panel displayed after you exit this panel. Table 11 shows
valid change values:
Table 11. Valid Point-and-Shoot Change Values
Color Choices Intensity Choices Highlight Choices
The panel text provides an overview of the command and its parameters. For a
complete description of the ENVIRON command and its parameters, see ISPF
Dialog Developer’s Guide and Reference.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Figure 50. Workstation Pull-Down on the ISPF Settings Panel Action Bar (ISPISMMN)
From this pull-down you can start a workstation session, specify GUI panel
settings, configure the Workstation Tool Integration dialog, download the ISPF C/S
component, and disconnect from the workstation.
Before you can perform these tasks, you must have completed the following:
v Successful installation and initialization of TCP/IP or APPC.
’Appendix B: Configuring Communications for the ISPF Client/Server’, in the
ISPF User’s Guide Volume I, contains procedures that will help you to test
whether you have satisfied this requirement.
v Successful installation of the ISPF Workstation Agent component.
See ’Appendix A: Installing the Client/Server component’, in the ISPF User’s
Guide Volume I for additional information.
v Initialization of the ISPF WSA component.
To initialize the WSA:
– If you have created a shortcut on your desktop that automatically launches
the WSA, double-click the icon.
If you do not have a shortcut icon:
1. Go to a command line in your operating system (Windows or Unix).
2. Change to the directory that contains your WSA executable file.
3. Enter WSA.
The Workstation Agent window is displayed on your workstation.
This window represents the executing ISPF C/S workstation program. For
more information about this window, see ’Appendix A: Installing the
Client/Server component’, in the ISPF User’s Guide Volume I. You can
minimize this window but you cannot close it while ISPF is running in GUI
mode.
Note: If you do not close the WSA window after you end an ISPF C/S
session, you will not have to repeat this step to start another ISPF C/S
session; that is, as long as the ISPF C/S component has been started,
you can start a workstation session.
Note: You can specify the GUI panel settings without having established a
workstation connection and without running in GUI mode. However, your
changes will not be seen until you next run GUI mode.
Workstation Connection
When you select “Workstation connection” from the Workstation pull-down, one of
two events can occur. Either the Initiate Workstation Session panel is displayed, or
ISPF tells you that a newer version of the Workstation Agent code is available (if
your system programmer has not disabled this feature).
Note: If your WSA is not running, this panel will appear but you will not be able
to establish a connection.
The Initiate Workstation Session panel allows you to specify that you want to start
a GUI session. Starting a GUI session from this panel if you are in split screen
mode or 3290 partition mode is not supported. If you select Workstation
connection, you must specify the information in the following fields, as
appropriate:
Save values in system profile?
The default for this setting is YES. Any changes to this field are saved in
the user’s system profile.
Workstation connection
Allows you to specify one of the following types of connections for your
workstation session:
With GUI display
A GUI interface is provided for this session.
Without GUI display
A standard ISPF type of interface is provided for this session.
GUI Network Protocol
The type of network you use to connect the workstation to the
host: TCP/IP or APPC.
You can also select the third option Use ISPDTPRF file, to specify that
ISPF get your network address from the file allocated to DD ISPDTPRF.
The file can be sequential or a member of a PDS, and it can be fixed
blocked (FB) or variable blocked (VB). Each line of the file should be
formatted as follows: userid WORKSTAT protocol_id:network_address,
where:
userid
user’s TSO userid
protocol_id
network protocol identifier, either ip for TCP/IP or lu for APPC.
network_address
workstation address
Host Codepage
The host codepage value used in translating data from the host to the
workstation. This value must be specified with a Host Character Set value if
it is to be used. If only one, or neither, of these values is specified, the
values from the terminal query are used. If your terminal or emulator does
not support codepages, the CODEPAGE and CHARSET parameter values
on the ISPSTART command are used. If the ISPSTART values are not
specified, the default codepage and character set is ENGLISH.
Host Character Set
The host character set value used in translating data from the host to the
workstation. This value must be specified with a Host Codepage value if it
is to be used. If only one, or neither, of these values is specified, the values
from the terminal query are used. If your terminal or emulator does not
support codepages, the CODEPAGE and CHARSET parameter values on
the ISPSTART command are used. If the ISPSTART values are not
specified, the default codepage and character set is ENGLISH.
GUI Window Frame
Allows you to specify one of the following types of window frames for
your GUI session:
1 Standard (STD). A GUI window frame that can be resized and that
has max/min buttons.
2 Fixed (FIX). A GUI window frame that has a min button but
cannot be resized.
3 Dialog (DLG). A GUI window frame that cannot be resized and
that does not have max/min buttons.
When you complete the fields shown in Figure 52 on page 68 and press Enter, the
WSA connection panel is displayed in a separate window (unless your system has
been set up to bypass it - see the section on the System Register panel in
“Appendix A: Installing the Client/Server component”, in the ISPF User’s Guide
Volume I for details).
This panel indicates the requestor and the type of connection requested. Click on
Yes to accept the connection as described, or No to reject the connection.
If you accept the connection, the ISPF Settings panel is displayed. This will be in
standard or GUI mode, depending on the option selected in the With GUI display
field.
Note: If you have not started the WSA, the Initiate Workstation Connection panel
displays, but you will not be able to establish a connection.
From this panel, you can download the latest WSA or continue to use your current
WSA, and even tell ISPF not to notify you again if your WSA does not match the
latest available. In the Download New Agent? field, you can specify one of three
choices:
Download now
The download copies an installation program for the latest level of the
WSA. You must specify the target directory in the “Directory to copy file
to:” field. To create a new directory (one that does not already exist on
your workstation) for the file, enter a slash mark (/) in the “Create
directory to which the file is to be copied” field. The “Data Set to copy file
from:” field should already be initialized by your system programmer. If it
is not, you must specify the host data set that holds the latest WSA
installation program. For example, ’SYS1.ISP.SISPGUI’.
After downloading the installation program for the WSA, end your
ISPF/GUI connection, terminate your old Workstation Agent, and run the
installation program to install the new one.
Do not download
You might want to download the new WSA later. If so, select “Do not
download”. ISPF does not download the new installation program at this
time, but will prompt you again the next time you start a GUI session. Of
course, you can always download the agent yourself with the
Client/Server Component download function of the ISPF Utilities panel at
any time. See “Download Data Set to Workstation Utility (Option 3.7)” on
page 192 for more information.
Cease warnings
ISPF does not download the agent installation program and you will not be
notified again that your current WSA does not match the latest available
on the host until an even higher level is available. That is, if you currently
run level 433 and you have asked to Cease warnings at level 440, ISPF will
not notify you again until at least level 441 is available.
Upon successful download of the new agent, the panel in Figure 55 appears. This
panel gives you the option to end your GUI session and begin the installation
immediately (by choosing option 1), or continuing your present session and
installing the new Workstation Agent at a later time. See “Download Data Set to
Workstation Utility (Option 3.7)” on page 192 for more information.
The GUI Settings pop-up window allows you to specify the following GUI
parameters:
Close Window
Allows you to specify that one of the following commands be processed
when you close a GUI window:
v CANCEL
v END
v EXIT
v RETURN.
Display Enter Key
Select this field to display an Enter push button at the bottom of all GUI
panels.
Accelerator Support
Select this field to use accelerator keys in this session.
3270 mode after losing workstation connection
Select this field if you want the ISPF session to continue in the 3270
emulator session rather than abend with code 989 when the workstation
connection is lost while running in GUI mode.
Download Images
Select this field to download images from the host library defined to
ddname ISPILIB, to the workstation image path. If you are not running
ISPF in GUI mode, this setting is ignored.
Make Path for Images
Select this field to have ISPF create the image path you specify, when the
image path you specify does not already exist on the workstation.
Path for images
In GUI mode, this field enables you to specify a workstation path for
images. The image path can be 244 characters long with no embedded
blanks. The image path you specify must follow the accepted path notation
for whichever operating system you are using. If you do not specify an
image path, ISPF puts the image requested into the workstation’s working
directory.
Starting the Tool Integration Dialog: Before you can use the tool integrator, you
must have installed and configured the Workstation Agent. See “Workstation
Connection” on page 67 for details on these prerequisite tasks.
You can run the tool integrator in either GUI mode or the standard ISPF mode. For
information about running ISPF in GUI mode, see the chapter on the ISPF user
interface in the ISPF User’s Guide Volume I.
Note: You cannot issue a WSDISCON command or service call while running the
workstation tool integration dialog.
You can display the Workstation Tool Integration Configuration panel, shown in
Figure 57 on page 76, using any of the following methods:
v Select Workstation Tool Integration from the Workstation pull-down.
v Select the Workstation choice on the action bars found on the Edit or View
panels, then choose Workstation Tool Integration.
v Type INT on any ISPF command or action line and press Enter.
You use this panel to begin to define how the ISPF actions interact with the
workstation applications, or just to look at the actions you have already defined.
The Tool Integrator Action Bar Choices: The following action bar choices are
available on the Workstation Tool Integration panel:
File
Edit... Calls the edit function to update the
parameters of a workstation action.
View... Displays the parameters of a particular
action.
Cancel changes Exit edit without updating the workstation
action.
Exit and Save Exit edit and save changes made to the
workstation action parameters.
Map
Extension
Displays the Extension Mapping window and starts the extension
mapping dialog. See “Extension Mapping” on page 78 for more
information.
After you choose to edit an action, the screen shown in Figure 58 is displayed.
Workstation Command
The workstation invocation command string or name. This can be the
actual command name of the workstation application, or a workstation
path and command name.
Additional Parameters
Additional parameters for the workstation command you defined in the
Workstation Command field.
Working Directory
The directory on the workstation that is defined to the host as the location
that is used when Workstation Edit is used. This directory is used to
temporarily store the host data when Edit or View on the workstation has
been selected, or to save workstation data when a workstation file has
been selected to be edited on the workstation. This directory is also used
when the workstation command is started.
If you do not specify a directory location, then the workstation edit
working directory defaults to the ISPF WSA’s defined working directory.
The default is the directory where the ISPF WSA is started (in OS/2® and
Windows), or the user’s home directory (in AIX, HP-UX, and SUN), not the
location of the DLL or executable.
Extension Mapping: The Map choice on the tool integrator action bar enables
you to specify a default character set (3 characters or less) to correlate host data set
types to a workstation file extension. The host data set type is the last qualifier of
the data set. These are frequently longer than 3 characters, while most workstation
file extensions are 3 or less. The Extension Mapping dialog panel, shown in
Figure 59, shows how certain host data set types map to their workstation file
extension counterparts.
2. in the Host Type field, type the last qualifier of the host data set to be mapped
3. in the Workstation Extension field, type the extension name to be used for the
temporary workstation file created
4. press Enter.
If you attempt to use a host data set on a workstation and you have not mapped
the data set type to one on your workstation, the first 3 characters of the data set
type are used by default.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Figure 60. Identifier Pull-Down on the ISPF Settings Panel Action Bar (ISPISMMN)
Message Identifier
You can specify that you want to display message identifiers in one of two ways:
v Select the Message identifier choice from the Identifier pull-down on the ISPF
Settings panel action bar, as shown in Figure 60.
OR
v Issue the ISPF system command MSGID ON.
When you select Message identifier... from the Identifier pull-down, the Message
Identifier panel is displayed, as shown in Figure 61.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===> MSGSET
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
If you select the Display message identifier option, the message identifier is set to
On. The identifier will now display within the message text whenever a long
message option is accessed (that is, when you enter the HELP command). Deselect
this choice (or issue the MSGID OFF command) to set the message identifier to
Off.
Note: This setting is temporary and will not be retained across ISPF sessions.
The Default setting for message identifier value controls whether or not this
identifier is turned on when an ISPF session is started.
Figure 62 on page 81 shows an error message on the ISPF Settings panel displayed
with the message identifier set to on.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Panel Identifier
You can specify that you want to display panel identifiers in one of two ways:
v Select the Panel identifier choice from the Identifier pull-down on the ISPF
Settings panel action bar, as shown in Figure 60 on page 79.
OR
v Issue the ISPF system command PANELID ON.
When you select Panel identifier... from the Identifier pull-down, the Panel
Identifier panel is displayed, as shown in Figure 63 on page 82.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===> PANSET
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
The Default setting for panel identifier value controls whether or not this identifier
is turned on when an ISPF session is started.
Note: This setting is temporary and will not be retained across ISPF sessions.
Figure 64 shows the ISPF Settings panel displayed with the panel identifier set to
On.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Screen Name
You can specify that you want to display the screen name in one of two ways:
v Select the Screen name choice from the Identifier pull-down on the ISPF Settings
panel action bar.
OR
v Issue the ISPF system command SCRNAME ON.
Notes:
1. This setting is temporary and will not be retained across ISPF sessions.
2. If the panel identifier has been set on, the screen identifier will not display.
When you select Screen identifier... from the Identifier pull-down, the Screen
Identifier panel is displayed, as shown in Figure 65.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===> SCRSET
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
The Default setting for screen identifier value controls whether or not this
identifier is turned on when an ISPF session is started.
Figure 66 shows the ISPF Settings panel displayed with the screen identifier set to
On.
Terminal Characteristics
Screen format 2 1. Data 2. Std 3. Max 4. Part
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
ISPF is shipped with View enabled. You can disable View, thus allowing only
Browse, by modifying the ISPF Configuration Table. You must set the keyword
IS_VIEW_SUPPORTED to NO. For more information, see the section on the ISPF
Configuration Table in the ISPF Planning and Customizing manual.
You can view or browse data that has the following characteristics:
v Record Format (RECFM):
– Fixed, variable (non-spanned), or undefined
Note: If you try to view a data set with RECFM=U, the Browse function is
substituted.
– Blocked or unblocked
– With or without printer control characters
v Logical Record Length (LRECL):
– For fixed-length records, up to 32 760 characters
Workstation File:
File Name . . . . .
Options
Initial Macro . . . . Confirm Cancel/Move/Replace
Profile Name . . . . . Browse Mode
Format Name . . . . . View on Workstation
Data Set Password . . / Warn on First Data Change
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Note: If you specify a volume serial on the View Entry Panel, you can browse a
single volume of a non-SMS multivolume data set.
Each character in the data that cannot be displayed is changed on the display to
either a period or a character that you have specified. Using the DISPLAY
command, you can specify whether printer carriage-control characters are to be
treated as part of the data, and thus displayed.
During Browse, four-way scrolling is available through the scroll commands. You
can also use the FIND and LOCATE commands to scroll to a particular character
string, line number, or symbolic label.
Whenever you enter a command, such as FIND or one of the scroll commands,
that puts the cursor under a character string in the data set, ISPF highlights that
character string. This highlighting occurs whether you type the command on the
command line and press Enter or press a function key that the command is
assigned to.
Ending Browse
To end a Browse data display, use the END command. This returns you to the
previous panel, which is either a member list display or the View Entry panel. If a
member list is displayed, the name of the member you just browsed is at the top
of the list. You can select another member from the list or enter the END command
again to return to the View Entry Panel.
When the View Entry Panel is displayed again, you can select another data set or
member, or you can use the END command to return to the ISPF Primary Option
menu.
the command is displayed after the string has been found, which allows you to
then change the operand and issue another FIND command.
BROWSE—Browsing Recursively
The BROWSE command allows you to browse another member of the same data
set. It also allows you to browse any other data set without ending your current
Browse session.
BROWSE [member]
where:
member
An optional member of the ISPF library or other partitioned data set that
you are currently browsing. You may enter a member pattern to generate a
member list.
If you do not specify a member name, the Browse Command - Entry Panel is
displayed.
You end a nested Browse session the same way you would a normal one. When
you end the nested Browse session, the current Browse session resumes.
COLUMNS—Identifying Columns
You can use the COLUMNS command to provide a temporary indication of where
columns occur on the panel. This command displays a column-identification line
on the first line of the data area. The command has the following syntax:
where:
ON The default. Displays the column-identification line.
OFF Removes the column-identification line from the display.
Note: You can also remove the column-identification line by entering the RESET
command.
You must enter at least one operand, but you can enter them in any order. If you
enter only one operand, the other operand retains its current value.
where:
char The character you want to use to represent characters that cannot be
displayed on the screen. It can be a single character, or a single character
enclosed in apostrophes (’) or quotation marks ("). If you specify a blank
as the character, you must enclose it in apostrophes or quotation marks.
CC Shows that carriage control characters are to be displayed and are to be
considered part of the data.
NOCC
Shows that carriage control characters are not to be displayed and are not
to be considered part of the data.
Both operands are stored in your user profile and are in effect whenever you are
using Browse. You need to reenter the DISPLAY command only if you want to
change one of the operands.
The first settings for display mode are period (.) and NOCC, but the carriage
control character status has no effect if the data that you are browsing has no
carriage control characters.
The following examples show three different ways to enter the DISPLAY
command:
v To use blanks to represent characters that cannot be displayed, enter:
DISPLAY " "
v To use a vertical bar (|) to represent characters that cannot be displayed, enter:
DISPLAY |
v To suppress the display of carriage control characters, enter:
DISPLAY NOCC
EDIT—Editing a Member
The EDIT command allows you to edit another member of the same data set. It
also allows you to edit any other data set without ending your current Browse
session.
EDIT [member]
where:
member
An optional member of the ISPF library or other partitioned data set that you
are currently browsing. You may enter a member pattern to generate a member
list.
if you do not specify a member name, the edit command - entry panel is
displayed.
You end a nested Edit session the same way you would a normal one. When you
end the nested Edit session, the current Browse session resumes.
Note: FIND as a Browse command, shown here, has the same syntax as FIND as
an Edit command, except the optional X/NX/EX and line range operands
are not included.
where:
string
Required operand. The character string you want to find.
NEXT | ALL | FIRST | LAST | PREV
Optional operands that define the starting point, direction, and extent of the
search. NEXT is the default.
CHARS | PREFIX | SUFFIX | WORD
Optional operand. Operands that set the conditions for a character string
match. CHARS is the default.
col-1 and col-2
Optional operands. Numbers that identify the columns the FIND command is
to search.
You can separate the operands with blanks or commas and you can type them in
any order, but col-2, if typed, must follow col-1.
Specifying Find Strings: The string operand specifies the characters to be found.
For examples of different string formats, refer to the description of the FIND
command in ISPF Edit and Edit Macros.
Generally, you enter the strings without delimiters. For example, to find all
occurrences of ABC, enter:
FIND ALL ABC
Using String Delimiters: You must use delimiters if a string contains embedded
blanks or commas, or if a string is the same as a command keyword. You delimit
strings with either apostrophes (’) or quotation marks ("). For example, to find the
next occurrence of every one, enter:
The FIND command does not find the apostrophe or quotation mark string
delimiters.
Note: The Browse FIND command does not work with a search argument that
contains the command delimiter, even if string delimiters are used. You can
specify a hexadecimal search string or use ISPF Option 0 to change the
command delimiter to a different character.
Starting Point, Direction, and Extent of Search: You can control the starting
point, direction, and extent of the search by using one of the following operands:
NEXT The scan starts at the first position after the current cursor location and
searches ahead to find the next occurrence of the string. NEXT is the
default.
ALL The scan starts at the top of the data and searches ahead to find all
occurrences of the string. A message in the upper-right corner of the screen
shows the number of occurrences found. The second-level message that is
displayed when you enter the HELP command shows which columns were
searched.
FIRST The scan starts at the top of the data and searches ahead to find the first
occurrence of the string.
LAST The scan starts at the bottom of the data and searches backward to find the
last occurrence of the string.
PREV The scan starts at the first position before the current cursor location and
searches backward to find the previous occurrence of the string.
If you specify FIRST, ALL, or NEXT, the direction of the search is forward; pressing
the RFIND function key (F5/17) finds the next occurrence of the designated string.
If you specify LAST or PREV, the direction of the search is backward; pressing the
RFIND function key finds the previous occurrence of the string. The other optional
operands remain in effect, as specified in the last FIND command. These operands
include CHARS, WORD, PREFIX, SUFFIX, and col-1, col-2.
The search proceeds until one or all occurrences of the string are found, or until
the end of data is found. If the string is not found, one of the following actions
takes place:
v If the FIND command was entered on the Command line, a NO string FOUND
message is displayed in the upper-right corner of the screen.
v If the FIND command was repeated using the RFIND command, either a BOTTOM
OF DATA REACHED message or a TOP OF DATA REACHED message is displayed,
depending on the direction of the search. When these messages appear, you can
press the RFIND function key again to continue the search by wrapping to the
top or bottom of the data. If the string is still not found anywhere in the data, a
NO string FOUND message is displayed.
In the following illustration, the underscored strings would be found and the
strings that are not underscored would be ignored:
Using Text Strings: Text strings are processed exactly the same as delimited
strings. They are provided for compatibility with prior versions of the product.
For example:
FIND C’XYZ’
If you specify a text string that contains any SO or SI characters, the string is
considered a character string.
If an APL or TEXT keyboard is being used, the following additional character can
be used in a picture string:
P’ ’ Any APL-specific or TEXT-specific character
P’_’ Any underscored alphabetic APL character and delta.
Only the special characters listed above are valid within a picture string, but the
string can include alphabetic or numeric characters that represent themselves.
A DBCS subfield cannot be specified as the subject of a picture string for the FIND
command.
When you use the special characters ’=’ or ’.’ and a nondisplayable character is
found, a hexadecimal representation is used in the confirmation message that
appears in the upper-right corner of the screen. For example:
FIND P’..’
Column Limitations: The col-1 and col-2 operands allow you to search only a
portion of each line, rather than the complete line. These operands, which are
integers separated by a comma or by at least one blank, show the starting and
ending columns for the search. The following rules apply:
v If you specify neither col-1 nor col-2, the search continues across all columns
within the current boundary columns.
v If you specify col-1 without col-2, the string is found only if it starts in the
specified column.
v If you specify both col-1 and col-2, the complete string, not just part of it, must
be within the specified columns.
Using RFIND: The RFIND command, which is usually assigned to the F5/17 key,
allows you to repeat the previous FIND command without retyping it. Therefore,
you can use this command to find successive occurrences of the string specified in
the last FIND command. You can also use the RFIND command to return to the
top of your data and continue searching when the BOTTOM OF DATA REACHED
message appears. If you enter the RFIND command on the Command line instead
of using a function key, you must position the cursor to the desired starting
location before pressing Enter.
If you specify a 1-byte hexadecimal string as the FIND string and the string is
found at the second byte of a double-byte character set (DBCS) character, hardware
sets the cursor to the first byte of the character. If you then request RFIND, the
same data is found again. To find the next occurrence of the string, you must move
the cursor to the next character position before requesting RFIND again.
where:
ON Turns hexadecimal mode on. This is the default.
OFF Turns hexadecimal mode off.
VERT Valid only when hexadecimal mode is ON. This is the default. Figure 70 on
page 97 shows how VERT causes the hexadecimal representation to be
displayed vertically, two rows per byte, under each character.
DATA Valid only when hexadecimal mode is ON. Figure 71 on page 97 shows
how DATA causes the hexadecimal representations to be displayed as a
string of hexadecimal characters, two per byte. Since the hexadecimal
string is twice the length of the data string, it consumes two rows. If you
omit this operand, VERT is assumed.
When using browse and placing the cursor anywhere within the record, SCROLL
UP positions the data where the cursor is located as the last complete line record
on the display. A complete line record consists of the standard character form line,
two hexadecimal character lines, and a separator line.
For example, the following command would display the hexadecimal notation
vertically:
HEX VERT
Three lines are displayed for each source line. The first line shows the data in
standard character form. Figure 70 on page 97 shows the next two lines with the
same data in vertical hexadecimal representation. A separator line is displayed
between the two representations to make it easier for you to read the data.
Figure 71 on page 97 shows the next two lines with the same data in DATA
hexadecimal representation.
You can use the FIND command to find invalid characters or any specific
hexadecimal character regardless of the setting of hexadecimal mode. Refer to the
syntax for picture strings and hexadecimal strings under the description of the
FIND command in ISPF Edit and Edit Macros.
------------------------------------------------------------------------------
:H3 ID=BRHEX SUBJECT=’BROWSE COMMANDS - HEX’.
7CF4CC7CDCCE4EECDCCE77CDDEEC4CDDDCDCE464CCE74
A83094E2985702421533ED296625036441542000857DB
------------------------------------------------------------------------------
HEX - DISPLAYING DATA IN HEXADECIMAL FORMAT
CCE464CCEDDCECDC4CCEC4CD4CCECCCCCDCD4CDDDCE
8570004927318957041310950857145394130669413
------------------------------------------------------------------------------
:P.THE DISPLAY OF DATA IN HEXADECIMAL NOTATION IS CONTROLLED BY THE HEX
7D4ECC4CCEDDCE4DC4CCEC4CD4CCECCCCCDCD4DDECECDD4CE4CDDEDDDDCC4CE4ECC4CCE
A7B38504927318066041310950857145394130563139650920365396335402803850857
------------------------------------------------------------------------------
------------------------------------------------------------------------------
:H3 ID=BRHEX SUBJECT=’BROWSE COMMANDS - HEX’.
7AC8F340C9C47EC2D9C8C5E740E2E4C2D1C5C3E37E7DC2D9D6E6E2C540C3D6D4D4C1D5C4E2406040
C8C5E77D4B
------------------------------------------------------------------------------
HEX - DISPLAYING DATA IN HEXADECIMAL FORMAT
C8C5E7406040C4C9E2D7D3C1E8C9D5C740C4C1E3C140C9D540C8C5E7C1C4C5C3C9D4C1D340C6D6D9
D4C1E3
------------------------------------------------------------------------------
:P.THE DISPLAY OF DATA IN HEXADECIMAL NOTATION IS CONTROLLED BY THE HEX
7AD74BE3C8C540C4C9E2D7D3C1E840D6C640C4C1E3C140C9D540C8C5E7C1C4C5C3C9D4C1D340D5D6
E3C1E3C9D6D540C9E240C3D6D5E3D9D6D3D3C5C440C2E840E3C8C540C8C5E7
------------------------------------------------------------------------------
LOCATE—Locating Lines
Use the LOCATE command to bring a particular line to the top of the display. You
can identify the line by either its relative line number or a previously defined label.
During Browse, the current position of the screen window is shown by the
line/column numbers in the upper-right corner of the screen. The line number
refers to the first line of data following the two header lines, and shows the
relative position of that line in the data. The Top of Data message is treated as
relative line zero. You must enter either a line number or a label as an operand.
where:
line-number
A numeric value of up to 8 digits that shows the position of the line from the
beginning of the data. The line number is displayed in the upper-right corner.
label
Defined by scrolling to the top of the screen the line with which you want to
associate the label. You then type the label on the command line in the form:
.ccccccc
For example, to find line 18463, you could enter the following command:
LOCATE 18463
ISPF then moves line 18463 to the top of the screen. You can assign a label to it by
entering:
.label
The latest assignment of a label overrides any previous assignments. You can
assign several labels to the same line. Labels are not retained when you leave the
Browse option.
Note: The Browse SUBMIT command is not supported if the underlying data is
packed.
VIEW—Viewing a Member
The VIEW command allows you to view another member of the same data set. It
also allows you to view any other data set without ending your current Browse
session.
VIEW [member]
where:
member
An optional member of the ISPF library or other partitioned data set that you
are currently browsing. You may enter a member pattern to generate a member
list.
If you do not specify a member name, the View Command - Entry Panel is
displayed.
You end a nested View session the same way you would a normal one. When you
end the nested View session, the current Browse session resumes.
If you have made a connection to the workstation, you can also specify a
workstation file name, for example C: \AUTOEXEC.BAT, on the Edit Entry Panel.
Or you can specify which environment (host or workstation) should be used to
edit a data set. With these options, one of four editing situations can occur:
v Edit a host data set on the host
v Edit a host data set on the workstation
v Edit a workstation file on the host
v Edit a workstation file on the workstation.
Note: Some file names are reserved or restricted depending on the workstation
operating system. An attempt to edit a file name that is reserved or
restricted by your operating system might cause your workstation operating
system or host system to hang. See your workstation operating system
documentation to learn restricted or reserved file names.
Edit a Host Data Set on the Host
The editor searches the ISPF libraries in the designated order to find the
member and copy it into working storage. If you specified a nonexistent
member of an ISPF library, a new member is created with the specified
name.
When you save the edited member, the editor places or replaces it in the
first ISPF library in the concatenation sequence, regardless of which library
it was copied from.
Edit a Host Data Set on the Workstation
The editor searches the ISPF libraries in the designated order to find the
member and copy it into working storage. The data set name is converted
to a workstation file name, and that name is appended to the workstation’s
current working directory. The host data set is transferred to the
workstation, and the working file is then passed to the user’s chosen edit
program.
When you finish the edit session, the working file is transferred back to the
host and stored in the first ISPF library in the concatenation sequence.
Edit a Workstation File on the Host
The editor searches the workstation files to find the desired file and copy it
into working storage. The workstation file name is converted to a host data
set name, and, if greater than 44 characters, it is truncated to be 44. The
workstation file is transferred to the host, where you can edit it.
When you finish the edit session, the working file is transferred back to the
workstation and stored.
Edit a Workstation File on the Workstation
This edit proceeds as it normally does on your workstation.
ISPF Library:
Project . . . MYPROJ
Group . . . . DEV . . . . . . . . .
Type . . . . SOURCE
Member . . . (Blank or pattern for member selection list)
Workstation File:
File Name . . . . .
Options
Initial Macro . . . . / Confirm Cancel/Move/Replace
Profile Name . . . . . Mixed Mode
Format Name . . . . . Edit on Workstation
Data Set Password . . Preserve VB record length
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Utilities For more information, see the section on the Utilities Action Bar
Choice in the ISPF User Interface chapter of the ISPF User’s Guide
Volume I.
Workstation Configure ISPF workstation tool integration.
Help The Help pull-down offers you the following choices:
1 General
2 Type of Data Sets
3 Edit entry panel
4 Member selection list
5 Display screen format
6 Scrolling data
7 Sequence numbering
8 Display modes
9 Tabbing
10 Automatic recovery
11 Edit profiles
12 Edit line commands
13 Edit primary commands
14 Labels and line ranges
15 Ending an edit session
16 Appendices
17 Index
data set name in apostrophes. However, if you omit the TSO user
prefix and apostrophes, your TSO user prefix is automatically
added to the beginning of the data set name.
If you specify a VSAM data set name, ISPF checks the
Configuration table to see if VSAM support is enabled. If so, the
specified tool is invoked. If VSAM support is not enabled, an error
message is displayed.
Volume Serial A real DASD volume or a virtual volume residing on an IBM 3850
Mass Storage System. To access 3850 virtual volumes, you must
also have MOUNT authority, which is acquired through the TSO
ACCOUNT command.
Workstation File:
If you have made a connection to the workstation, you can specify
a workstation file name, for example C: \AUTOEXEC.BAT, in this
field.
Initial Macro You can specify a macro to be processed before you begin editing
your sequential data set or any member of a partitioned data set.
This initial macro allows you to set up a particular editing
environment for the Edit session you are beginning. This initial
macro overrides any IMACRO value in your profile.
If you leave the Initial Macro field blank and your edit profile
includes an initial macro specification, the initial macro from your
edit profile is processed.
If you want to suppress an initial macro in your edit profile, type
NONE in the Initial Macro field. See the sections on Initial Macros
and the IMACRO primary command in the ISPF Edit and Edit
Macros manual for more details.
Profile Name The name of an edit profile, which you can use to override the
default edit profile. See the sections on Edit Profiles and the edit
environment in the ISPF Edit and Edit Macros manual.
Format Name The name of a format definition or blank if no format is to be
used.
Data Set Password
The password for OS password-protected data sets. This is not
your RACF password.
Confirm Cancel/Move/Replace
When you select this field with a ″/″, a confirmation panel
displays when you request one of these actions, and the execution
of that action would result in data changes being lost or existing
data being overwritten.
v For MOVE, the confirm panel is displayed if the data to be
moved exists. Otherwise, an error message is displayed.
v For REPLACE, the confirm panel is displayed if the data to be
replaced exists. Otherwise, the REPLACE command functions
like the edit CREATE command, and no confirmation panel is
displayed.
v For CANCEL, the confirmation panel is displayed if any data
changes have been made, whether through primary commands,
line commands, or typing.
Menu Help
──────────────────────────────────────────────────────────────────────────────
Utility Selection Panel
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
12 Appendices
13 Index
ISPF allocates the IEBCOPY SYSUT3 and SYSUT4 data sets as one primary
cylinder, one secondary cylinder. If this is not sufficient for your compress request,
these DDNAMES can be preallocated.
For sequential data sets, options I and S display the same information. For
multivolume data sets, options I and S display current allocation and utilization
values that represent totals from all volumes used. You may not enter a volume
serial when you are requesting information on a multivolume data set.
The space for data sets allocated in blocks is calculated as if all of the tracks,
including the last one, contain only full blocks of data. Any partial “short” blocks
are ignored.
Note: The information shown for current space utilization is the actual data that
the data set contains, based on the number of allocation units (blocks, tracks,
bytes, megabytes, and so on) that have been written. For a data set allocated
in units other than tracks and cylinders, it does not include the unused
portion of a track that is only partially filled. For example, if a data set
allocated in bytes with block size of 600 has one block written to a device
with a track size of 1000, 600 bytes of data are written and the remaining
400 bytes cannot be used by a different data set. A track is the smallest
possible unit of physical allocation to a data set on DASD. ISPF reports 600
bytes used while other products (such as ISMF) report 1000 bytes used. ISPF
reports the space occupied by data in the data set. ISMF reports the space
used by this data set that is not available for use by another data set. The
difference is a relative indication of the effectiveness of the block size used
when the data set was created.
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F12=Cancel
If the volume serial is followed by a plus (for example, HSM016+), the data set
spans multiple volumes. Press Enter to display a list of all allocated volumes that
have been used, as shown in Figure 77.
The “Allocated units” and “Used units” fields can vary, depending on the value
that was specified in the “Space units” field when you allocated the data set. For
example, Figure 77 shows what the Data Set Information panel would look like if
the data set was allocated by specifying Cylinders in the “Space units” field.
Information for Managed Data Sets: The Library Utility option I (Figure 78)
displays information for data sets that reside on Storage Management Subsystem
Volumes (also called managed data sets) when:
v Data Facility Product (DFP) Version 3 Release 2 or later is installed and
available.
v Storage Management Subsystem is active.
v Directory block information is available.
Figure 78. Data Set Information for Managed Data Sets (ISRUAISE)
If the volume serial is followed by a plus (for example, HSM016+), the data set
spans multiple volumes.
Note: SMS-managed multivolume data sets will not display a plus unless data has
been written past the first volume.
Press Enter to display a list of all allocated volumes as shown in Figure 79 on page
114.
Volume Information
D
More: +
G All allocated volumes: Allocation
More: + ated tracks . : 32
ated extents . : 32
HSM017 HSM018 HSM019 HSM020 HSM021
Utilization
tracks . . . . : 31
Command ===> extents . . . : 31
F1=Help F2=Split F3=Exit
F7=Backward F8=Forward F9=Swap
Secondary tracks . . : 17
Data set name type . : 1
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward
F9=Swap F12=Cancel
Figure 79. Volume Information for a Managed Multivolume Data Set (ISRUAMVI)
The major difference between this information and the information that is
displayed for data sets on non-managed volumes is the addition of the following
classes:
v Management class
v Storage class
v Data class.
If directory block information is not available, the Data Set Information panel
shows a value of 0 * for the “Maximum dir. blocks”, “Used dir. blocks”, and
“Number of members” fields. The asterisk beside the zero refers you to a note on
the panel, which states that the directory is unavailable.
If the data set is a PDSE, the “Data set name type” field is LIBRARY and the
“Maximum dir. blocks” field is NOLIMIT. Because the used blocks, used extents,
and used directory blocks are not applicable to a PDSE, the Data Set Information
panel replaces these values with “Used pages” and “% utilized” (Figure 80 on page
115). Other values that can appear in the “Data set name type” field are:
v HFS - MVS Hierarchical File System data set
v EXTENDED - DFP Striped data set.
Note: When a PDSE data set is created, it sets aside five pages. This may cause a
significant “% utilized” value for a small data set.
Figure 80. Data Set Information for PDSE Managed Data Sets (ISRUAISE)
The space for data sets allocated in blocks is calculated as if all of the tracks,
including the last one, contain only full blocks of data. Any partial “short” blocks
are ignored.
Note: The information shown for current space utilization is the actual data that
the data set contains, based on the number of allocation units (blocks, tracks,
bytes, megabytes, and so on) that have been written. For a data set allocated
in units other than tracks and cylinders, it does not include the unused
portion of a track that is only partially filled. For example, if a data set
allocated in bytes with block size of 600 has one block written to a device
with a track size of 1000, 600 bytes of data are written and the remaining
400 bytes cannot be used by a different data set. A track is the smallest
possible unit of physical allocation to a data set on DASD. ISPF reports 600
bytes used while other products (such as ISMF) report 1000 bytes used. ISPF
reports the space occupied by data in the data set. ISMF reports the space
used by this data set that is not available for use by another data set. The
difference is a relative indication of the effectiveness of the block size used
when the data set was created.
Figure 81 shows a short format example of data set information for a partitioned
data set. This is the short format ISPF uses to display data set information when
Data Facility Product (DFP) Version 3 Release 2 or later is not installed or
available, or when the Storage Management Subsystem is not active. See “Short
Information for Managed Data Sets” to see how ISPF displays data set information
when these products are installed, available, and active.
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F12=Cancel
The “Allocated units” and “Used units” fields can vary, depending on the value
that was specified in the “Space units” field when you allocated the data set. For
example, Figure 81 shows what the short format of the Data Set Information panel
would look like if the data set was allocated by specifying CYLS in the “Space
units” field.
Short Information for Managed Data Sets: The Library Utility option S displays
information (Figure 82 on page 117) for data sets that reside on Storage
Management Subsystem volumes (also called managed data sets) when:
v Data Facility Product (DFP) Version 3 Release 2 or above is installed and
available
v Storage Management Subsystem is active.
Figure 82. Data Set Information (Short) for Managed Data Sets (ISRUAISE)
The major difference between this information and the information that is
displayed for data sets on non-managed volumes is the addition of the following
classes:
v Management class
v Storage class
v Data class.
If the data set is a PDSE, the “Data set name type” field is LIBRARY. Because the
used blocks and used extents are not applicable to a PDSE, the Data Set
Information panel replaces these values with “Used pages” and “% Utilized”
(Figure 83 on page 118). Other values that can appear in the “Data set name type”
field are:
v HFS - MVS Hierarchical File System data set
v EXTENDED - DFP Striped data set. When the Data Set Name Type is
EXTENDED, the SMS Compressible field indicates if the data set is compressible
or not (YES or NO).
B — Browse Member
If you select option B, you must specify a partitioned data set and a member
name. The specified member is displayed in Browse mode. You can use all the
Browse commands. When you exit Browse, the Library Utility panel reappears.
C — Copy Member
If you select option C, the copy prompt panel appears where you must specify a
partitioned data set and member name for the new member. When you exit Copy,
the Library Utility panel reappears.
D — Delete Members
If you select option D, you must specify a partitioned data set and a member name
or pattern. Option D prevents you from deleting a PDS member that any user is
currently editing.
If you have selected Confirm Member Delete on the Library Utility panel
(ISRUDA1), then you are asked to confirm your intention to delete this member.
Note that Confirm Delete is forced on when deleting members by pattern.
E — Edit Member
If you select option E, you must specify a partitioned data set and member name.
The specified member is displayed in Edit mode. You can use all EDIT commands.
When you exit Edit, the Library Utility panel reappears.
G — Reset Member
If you select option G, the reset prompt panel displays, where you enter the data
set and member name. When you exit, the Library Utility panel reappears.
M — Move Member
If you select option M, the move prompt panel displays, where you enter the data
set and member name. When you exit, the Library Utility panel reappears.
P — Print Member
If you select option P, you must specify a partitioned data set and a member name.
A source listing of the member is recorded in the ISPF list data set.
Note: If any members are to be printed, the data set characteristics must conform
to those for the L option.
R — Rename Member
If you select option R, you must specify a partitioned data set and member name.
You must also specify a new member name in the “New name” field. Option R
prevents you from renaming a member that is currently being edited by you or
another user.
V — View Member
If you select option V, you must specify a partitioned data set and member name.
The specified member is displayed in View mode. You can use all EDIT
commands. When you exit View, the Library Utility panel reappears. For more
information, see chapter on the View (Option 1) in ISPF User’s Guide Volume I.
ISPF Library:
Project . . Enter "/" to select option
Group . . . / Confirm Data Set Delete
Type . . . .
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
DASD-resident sequential or partitioned data set. For the other options, you can
specify any DASD-resident data set that is not VSAM. You can get short
information on a VSAM data set.
Note: You cannot assign a password to a managed data set. Therefore, the Data
Set Password field is ignored when you allocate a managed data set.
4. Press Enter.
The Allocate New Data Set panel is displayed. This panel enables you to specify
data set allocation values. The fields displayed on this panel depend upon the
value of the ALLOWED_ALLOCATION_UNITS keyword in the ISPF configuration
table. When ALLOWED_ALLOCATION_UNITS is not ’A’ the panel shown in
Figure 85 on page 122 is displayed.
Figure 86. Allocate New Data Set —Managed Data Set Support Panel (ISRUAASE)
When you press Enter with this panel displayed, the new data set is allocated and
cataloged. Entering the END command returns you to the previous panel without
allocating the data set.
An optional installation exit, the data set allocation exit, can control all data set
creation, deletion, allocation, and deactivation done directly by ISPF. This does not
include allocations done by ISPF, the TSO ALLOCATE command, or other TSO
commands. Refer to ISPF Planning and Customizing for more information about the
data set allocation exit.
Your installation must use the Data Facility Product (DFP) or DFSMS/MVS® to
define the values that you enter in the “Management class”, “Storage class”, and
“Data class” fields. If you have no specific requirements, you can leave these fields
blank. However, be aware that your installation may provide default management,
storage, and data classes. These defaults would take effect if you leave any of the
class fields blank and may even override any classes that you specify.
Management class
Used to obtain data management-related information (migration, backup,
and retention criteria, such as expiration date) for the data set allocation.
If you have no specific management class requirements, you can leave this
field blank. However, be aware that your installation may provide a
default management class. This default may even override any
management class that you specify.
Storage class
Used to obtain the storage-related information (volume serial) for the data
set allocation. Any volume serial that you enter in the “ Volume serial”
field is ignored unless the storage class that you use includes the
Guaranteed Space=Yes attribute (useful if you are allocating multivolume
data sets).
Data class
Used to obtain the data-related information (space units, primary quantity,
secondary quantity, directory block, record format, record length, and data
set name type) for the allocation of the data set.
Default values are provided for the fields in Figure 85 on page 122, except for
expiration date, based on which of the following occurred most recently:
v What you last entered on this panel
v The last display data set information request (options 3.1, 3.2, or 3.4).
You can type over the displayed defaults if you want to change them. The
following is a list of the fields on this panel and their definitions:
Volume serial
This field is one that you probably will not need to use very often. It is not
required and is usually ignored by the Storage Management Subsystem.
You should not enter a volume serial if you want to do one of the
following:
v Use the authorized default volume.
v Enter a generic unit address in the Generic unit field.
v Use the volume specified by the storage class you are using.
When a storage class is used, your installation and the SMS assume joint
responsibility for determining the volume on which the data set is
allocated. The SMS enables the installation to select the volumes that are
eligible to contain the data set. It then chooses one of those volumes and
allocates the data set. The SMS’s volume choice is based on:
v storage requirements
v the amount of space a volume has available.
Generic unit
The generic unit address for the direct access volume that is to contain the
data set, such as 3380, 3390, and so forth. This field overrides the Volume
Serial field on the Data Set Utility panel. Therefore, you should leave this
field blank if you want to do one of the following:
v Use the authorized default volume
v Enter a volume serial in the Volume serial field.
Notes:
1. Leave both the Volume serial and Generic unit fields blank to allow
ISPF to select an eligible volume. Eligibility is determined by the unit
information in your user entry in the TSO User Attribute Data Set
(UADS) or the TSO segment of RACF.
2. At some installations, you are limited to eligible volumes even when an
explicit volume serial is specified. At other installations you can specify
any mounted volume. This is an installation option.
3. To allocate a data set to a 3850 virtual volume, you must also have
MOUNT authority, gained by using the TSO ACCOUNT command or
by using the RACF PERMIT command for the TSO AUTH general
resource class.
4. If you are allocating an SMS data set, you can enter either an
installation defined group name or a generic device type in the Generic
unit field, but not a specific device number.
Space units
Any of the following:
Track Shows that the amounts entered in the primary and
secondary quantity fields are expressed in tracks.
Cylinder Shows that the amounts entered in the primary and
secondary quantity fields are expressed in cylinders.
Block Shows that the amounts entered in the primary and
secondary quantity fields are expressed in blocks.
Megabyte Shows that the amounts entered in the primary and
secondary quantity fields are expressed in megabytes.
Kilobyte Shows that the amounts entered in the primary and
secondary quantity fields are expressed in kilobytes.
Byte Shows that the amounts entered in the primary and
secondary quantity fields are expressed in bytes.
Records Shows that the amounts entered in the primary and
secondary quantity fields are the average number of
records of the size specified by the block size field.
Note: “Space units” allows the shortest unique abbreviation for each
attribute; for example, T for TRKS, C for CYLS, K for KB, and M for
MB, BY for BYTE, R for RECORDS, and BL for BLKS.
Average record unit
Shows the unit used when allocating average record length. U specifies
single-record units (bytes). K specifies thousand-record units (kilobytes). M
specifies million-record units (megabytes). The default value is U.
Primary quantity
The primary allocation quantity in tracks, cylinders, blocks, megabytes,
Note: The record length and block size are verified to be consistent with
the record format, as defined in OS/VS2 MVS Data Management
Services Guide. If you need to use non-standard characteristics, use
the TSO ALLOCATE command.
Expiration date
Allows you to protect valuable data by specifying a date, in your national
language, when the data set may be deleted. If you try to delete an
unexpired data set, ISPF displays two panels: a Confirm Delete panel,
followed by a Confirm Purge panel. See “D — Delete Entire Data Set” on
page 132 for more information about deleting unexpired data sets.
An expiration date is not required, but if you enter one it should be in one
of the following formats:
YY/MM/DD, YYYY/MM/DD
Date shown in year, month, and day, or your equivalent national
format. The maximum expiration date allowed is:
v 99/12/31 for a 2-digit year
v 2155/12/31 for a 4-digit year.
YY.DDD, YYYY.DDD
Date shown in Julian format, such as 86.045 for February 14, 1986.
The maximum expiration date allowed is:
v 99.365 for a 2-digit year
v 2155.365 for a 4-digit year.
Note: When specifying an expiration date beyond 99/12/31, you must use
the 4 character year format. For example, specify 2000/06/21 instead
of 00/06/21.
Allocate Multiple Volumes
Allows you to allocate sequential data sets that span multiple volumes.
ISPF supports a maximum of 59 volumes. Place a slash in this field and
press enter to display a panel similar to the one shown in Figure 87 on
page 127.
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Allocation Errors
ISPF attempts to recognize inconsistent attributes for partitioned and sequential
data sets before allocating them. However, the Allocation Error panel (Figure 88 on
page 128) appears when conditions that ISPF has no control over allow the
allocation of such a data set. These conditions are caused by:
v A data class that specifies inconsistent attributes
v Attributes entered on the Allocate New Data Set panel that create inconsistency
by overriding other attributes specified by the data class.
Instructions:
Press the Enter key to DELETE the data set.
For information about allocation errors and how they affect data set promotion
when using SCLM, refer to ISPF Software Configuration and Library Manager (SCLM)
Project Manager’s and Developer’s Guide.
The term inconsistent attributes refers to incompatible values that have been
specified for one or more of the following:
v Space units
v Primary quantity
v Secondary quantity
v Directory blocks
v Record format
v Record length
v Block size.
For example, if you allocate a data set with an undefined record format
(RECFM=U) and a block size of zero (BLOCKSIZE=0), certain ISPF functions and
services cannot use the data set. These functions and services include:
v Move and copy functions
v LMMOVE, LMCOPY, and LMINIT services.
However, when either the linkage editor or the IEBCOPY utility has been called,
these functions and services determine the best block size for the data set. Then,
when the data set has a block size greater than zero, the ISPF functions and
services listed above can be used.
The Allocation Error panel gives you the opportunity to delete such a data set
because other ISPF functions, such as View (option 1) and Edit (option 2), may not
be able to use it.
The sample panel (Figure 88) shows this error message example:
Specified data set has zero block size
Press Enter to delete the data set or enter the END command to keep the data set.
The preceding instructions for cataloging data sets do not apply to data sets that
reside on Storage Management Subsystem volumes. These data sets are
automatically cataloged when you allocate them. They cannot be cataloged by
using option C.
┌─────────────────────────────────────────────────────────────────────────┐
─ │ ISRUARP1 Rename Data Set │
│ │
│ Data Set Name . . : MYPROJ.DEV.SOURCE │
│ Volume Serial . . : MVS8WF │
│ │
│ Enter new name below: (The data set will be recataloged.) │
b │ │
│ ISPF Library: │
I │ Project . . MYPROJ │
│ Group . . . DEV │
│ Type . . . . SOURCE │
│ │
│ Other Partitioned or Sequential Data Set: │
O │ Data Set Name . . . │
│ │
│ │
│ │
D │ │
│ │
│ Command ===> │
O │ F1=Help F2=Split F3=Exit F7=Backward F8=Forward │
│ F9=Swap F10=Actions F12=Cancel │
F └─────────────────────────────────────────────────────────────────────────┘
Type the new data set name and press Enter to rename, or enter the END
command to cancel. Either action returns you to the previous panel.
If you specify a volume serial for a data set to be renamed, ISPF checks to see
whether the data set is cataloged on that volume. If it is, the Rename panel
prompts you to specify whether to recatalog the data set. The displayed default for
that field is YES. If you specify a volume serial and the data set is not cataloged, it
remains uncataloged after you rename it. If a volume serial is not specified, the
data set is recataloged to the new data set name and the old data set name is
uncataloged.
Notes:
1. ISPF does not rename VSAM data sets or password-indicated data sets.
2. A volume serial is not allowed for multivolume data sets using Rename.
Renaming GDG Data Sets: Generation Data Group (GDG) data sets can only be
renamed to something other than GDG names. Trying to rename GDG data sets to
a different generation or version number can cause deletion of your GDG data set
or group of GDG data sets.
Renaming Managed Data Sets: When you rename a data set that resides on a
Storage Management Subsystem volume, you cannot specify a volume serial in the
Volume Serial field. Both the cataloged entry and the VTOC entry are renamed.
Rename Processing with RACF: The normal order of processing when ISPF is
asked to rename a data set is as follows:
1. The new data set name is cataloged using SVC 26
2. The data set is renamed using SVC 30
3. The old data set name is uncataloged using SVC 26
There are three occasions, however, when ISPF will deviate from this order of
processing:
v If the data set is a System Managed (SMS) data set, the update of the catalog
(both cataloging the new name and uncataloging the old name) is handled by
the operating system when the SVC 30 is issued. In this case, ISPF does not
issue either of the SVC 26 requests.
v If the data set is an uncataloged data set, no catalog update will be done. The
data set is renamed using the SVC 30 only.
v If the data set is cataloged, but the user specified both the data set name and
volume, panel ISRUARP2 is displayed. The user has the option of specifying
whether the catalog processing should be done. If the user indicates (via a NO
in the “Reply to uncatalog the data set” field) that no catalog processing should
be done, only the SVC 30 is used to rename the data set. If the reply is YES, the
SVC 30 as well as both SVC 26 requests are issued.
The above order of processing is being used to minimize the possibility that an
uncataloged data set will result if an error is encountered during the rename
process. Errors may be encountered due to certain combinations of RACF data set
profiles and user access to the groups under which those data set profiles fall.
When an error occurs, the user receives a message indicating the status of the data
set name, and of the catalog entries.
Renaming with Expiration Dates: If the data set has an expiration date in its
catalog entry, the expiration date is not propagated forward to the new catalog
entry. The new catalog entry must be updated manually to specify the new
expiration date. Use the TSO ALTER command or a similar function to do this.
If you select this option, a panel appears to remind you of the situation (Figure 90).
Confirm Rename
Warning: The data set being renamed contains an expiration date in its catalog
entry. The expiration date will not be carried forward to the new catalog
entry. The expiration date can be set by using the TSO ALTER command.
Instructions:
Command ===>
F1=HELP F2= F3=END F4=DATASETS F5=FIND F6=CHANGE
F9=SWAP F10=LEFT F11=RIGHT F12=SUBMIT
Confirm Uncatalog
CAUTION:
The catalog entry being deleted has an expiration date which has not expired.
Instructions:
Command ===>
F1=HELP F2= F3=END F4=DATASETS F5=FIND F6=CHANGE
F9=SWAP F10=LEFT F11=RIGHT F12=SUBMIT
You cannot use option U to uncatalog a data set that resides on a Storage
Management Subsystem volume. However, the system uncatalogs these data sets
when you delete them, which is done by using option D of either the Data Set
utility (option 3.2) or the Data Set List utility (option 3.4).
If you specify a volume serial for the data set to be deleted, ISPF checks to see
whether the data set is cataloged on that volume. If so, the Confirm Delete panel
prompts you to specify whether to uncatalog the data set. The displayed default is
YES. If no volume serial is specified, and the data set does not have an expiration
date, the data set is deleted and uncataloged.
Notes:
1. ISPF does not delete password-protected data sets or data sets allocated with
an esoteric device type.
2. A volume serial is not allowed for multivolume data sets using Delete.
If the data set has an expiration date that has not expired, ISPF displays a Confirm
Purge panel (Figure 93 on page 134) after the Confirm Delete panel.
Use a slash to select Purge Data Set if you want ISPF to purge the data set. The
statement that is enclosed in parentheses on the Confirm Purge panel shows
whether the data set to be purged will be uncataloged.
When you delete a data set, the volume name is compared to the volume name in
the configuration table. If the names match, the command specified in the
configuration table is used in place of the ISPF delete processing. This lets you
delete migrated data sets without first causing them to be recalled.
Delete Processing with RACF: If the data set is an SMS data set, it is deleted
using SVC 29. The update of the catalog entry is handled by the operating system.
If the data set is not an SMS data set and either it is not cataloged or the user
indicates on panel ISRUADC2 (panel ISRUADC2 is shown if the volume is
supplied) that it is not to be uncataloged, it is deleted using SVC 29.
If the data set is not an SMS data set and it is cataloged and/or the user indicates
on panel ISRUADC2 (panel ISRUADC2 is shown if the volume is supplied) that it
is to be uncataloged, the following process is followed.
1. The data set is deleted using SVC 29 (SCRATCH).
2. The data set is uncataloged using SVC 26.
any discrete and/or generic data set profiles involved and to the catalogs involved.
Be aware that a discrete data set profile is deleted when the data set is deleted.
The space for data sets allocated in blocks is calculated as if all of the tracks,
including the last one, contain only full blocks of data. Any partial “short” blocks
are ignored.
Note: The information shown for current space utilization is the actual data that
the data set contains, based on the number of allocation units (blocks, tracks,
bytes, megabytes, and so on) that have been written. For a data set allocated
in units other than tracks and cylinders, it does not include the unused
portion of a track that is only partially filled. For example, if a data set
allocated in bytes with block size of 600 has one block written to a device
with a track size of 1000, 600 bytes of data are written and the remaining
400 bytes cannot be used by a different data set. A track is the smallest
possible unit of physical allocation to a data set on DASD. ISPF reports 600
bytes used while other products (such as ISMF) report 1000 bytes used. ISPF
reports the space occupied by data in the data set. ISMF reports the space
used by this data set that is not available for use by another data set. The
difference is a relative indication of the effectiveness of the block size used
when the data set was created.
See “Short Information for Managed Data Sets” on page 116 to learn more about
the data set information that is displayed for managed data sets.
The space for data sets allocated in blocks is calculated as if all of the tracks,
including the last one, contain only full blocks of data. Any partial “short” blocks
are ignored.
Note: The information shown for current space utilization is the actual data that
the data set contains, based on the number of allocation units (blocks, tracks,
bytes, megabytes, and so on) that have been written. For a data set allocated
in units other than tracks and cylinders, it does not include the unused
portion of a track that is only partially filled. For example, if a data set
allocated in bytes with block size of 600 has one block written to a device
with a track size of 1000, 600 bytes of data are written and the remaining
400 bytes cannot be used by a different data set. A track is the smallest
possible unit of physical allocation to a data set on DASD. ISPF reports 600
bytes used while other products (such as ISMF) report 1000 bytes used. ISPF
reports the space occupied by data in the data set. ISMF reports the space
used by this data set that is not available for use by another data set. The
difference is a relative indication of the effectiveness of the block size used
when the data set was created.
See “Information for Managed Data Sets” on page 113 for information about the
data set information that is displayed for managed data sets.
V — VSAM Utilities
Use option V to create the IDCAMS commands to define, delete, and list catalog
information for VSAM data sets. Before the command is issued, you will be
allowed to edit it in an ISPF Edit session. The command will process in the
foreground.
Note: The VSAM utilities function builds a command that is syntactically correct;
the utility does not do any compatibility checking of the fields used to build
the command.
When you select option V, the panel shown in Figure 94 is displayed.
┌────────────────────────────────────────────────────────────────────────┐
─ │ Menu Utilities Help │ ─
│ ───────────────────────────────────────────────────────────────────── │
│ VSAM Utilities │
│ More: + │
│ Process Request Data Type │
│ 1. Define 1. Alias │
b │ 2. Delete 2. Alternate Index │
│ 3. Information (Listcat) 3. Cluster │
I │ 4. Generation Data Group │
│ 5. Non-VSAM │
│ 6. Page Space │
│ 7. Path │
│ 8. User Catalog │
O │ 9. Data * │
│ 10. Index * │
│ 11. NVR ** │
│ 12. Truename ** │
D │ 13. VVR ** │
│ * Listcat Only │
│ Command ===> │
O │ F1=Help F2=Split F3=Exit F7=Backward F8=Forward │
│ F9=Swap F10=Actions F12=Cancel │
F └────────────────────────────────────────────────────────────────────────┘
VSAM Utilities Panel Action Bar: The VSAM Utilities panel action bar choices
function as follows:
Menu For more information, see the section on the Menu Action Bar Choice in
the ISPF User Interface chapter of the ISPF User’s Guide Volume I.
Utilities
For more information, see the section on the Utilities Action Bar Choice in
the ISPF User Interface chapter of the ISPF User’s Guide Volume I.
Help The Help pull-down offers you the following choices:
1 VSAM Utilities
VSAM Utilities Panel Fields: There are two fields on the VSAM Utilities panel:
Process Request
Required field. Indicates what is going to be done to the VSAM data set:
1 Define. Process an IDCAMS define request
2 Delete. Process an IDCAMS delete request against one or more
data sets.
3 Listcat. Process an IDCAMS list catalog request.
VSAM Data Type
Required field. Indicates what kind of data set is to be defined, deleted or
listed:
1 Alias. Define, delete, or list an alternate name for a non-VSAM
data set or a user catalog
2 Alternate Index. Specify that an alternate index is to be defined,
deleted, or listed or that an alternate index entry is to be
recataloged
3 Cluster. Specify that a cluster is to be defined, deleted, or listed or
that a cluster entry is to be recataloged
4 Generation Data Group. Specify that a generation data group
entry is to be defined, deleted, or listed
5 Non-Vsam. Specify that a non-VSAM, non-SMS-managed data set
is to be defined, deleted, or listed
6 Page Space. Specify that a page space is to be defined, deleted, or
listed
7 Path. Specify that a path is to be defined, deleted, or listed or that
a path entry is to be recataloged
8 User Catalog. Specify that a catalog is to be defined, deleted, or
listed
9 Data. List data level information (Listcat request only)
10 Index. List index level information (Listcat request only)
11 NVR. Delete an SMS-managed non-VSAM volume record entry
(Delete request only)
12 Truename. Delete the truename entry for a data or index
component of a cluster or alternate index or the name of an
alternate index (Delete request only)
13 VVR. Delete an unrelated VSAM volume record entry (Delete
request only).
Notes:
1. Select the Edit IDCAMS command option to edit the IDCAMS command that
this process generates before the command is issued. If you do not select this
option, the command will be issued when you press Enter.
2. Select the Browse errors only option to browse the output from IDCAMS only
when a nonzero return code is returned by IDCAMS.
Fill in the required fields or use a VSAM profile data set as described in “Building
a VSAM Profile Data Set” on page 139. When you press Enter, the screen shown in
Figure 96 on page 139 is displayed.
Note: If you try to use a profile that was defined for a different request type (for
example, Generation Data Group), you will receive a Type mismatch error.
Instructions:
When you are ready to process the command, type EXEC on the Command line and
press Enter. If the command processes with a nonzero return code, the panel
shown in Figure 97 is displayed.
Press F3 to return to the panel shown in Figure 96, make the necessary changes,
and resubmit the command.
Building a VSAM Profile Data Set: You can build a VSAM profile data set, each
member of which can be used to store input fields on a VSAM input panel for
later retrieval to the same panel. If you try to use a profile that was defined for a
different request type (for example, Generation Data Group), you will receive a
Type mismatch error.
When you have filled in a VSAM input panel, select the Save to Profile choice
from the Functions pull-down on the input panel action bar as shown in Figure 98.
ISPF displays a panel that allows you to assign a name to the profile data set
member, as shown in Figure 99 on page 141.
Type in the member name. When you press Enter, the data set will be created for
you (variable blocked, LRECL 203, PDS).
Using a VSAM Profile Data Set: When you have displayed a VSAM input panel,
select the Get from Profile choice from the Functions pull-down on the input panel
action bar to display the panel shown in Figure 100.
When you select a profile and press Enter, the fields on the entry panel will fill
with the values stored in the profile data set member.
Changing the VSAM Profile Data Set: To change the name of the active VSAM
profile data set, select the Change Profile Data Set choice from the Functions
pull-down on an input panel action bar to display the panel shown in Figure 101.
Figure 101. Panel for Changing the Name of the VSAM Profile Data Set (ISRUVGET)
You may type the name of a different profile data set. When you press Enter, the
data set is created if it does not exist, and this data set becomes the active profile
data set.
If you request a member list or specify an asterisk (*) in the Member field on the
“From” panel, ISPF does not display a Member field on the “To” panel. See the
Member Selection List Commands section of the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I for information about primary and line commands
that are available for the Move/Copy utility member list display.
You can copy or move load modules stored in partitioned data sets with undefined
record formats, but you cannot print them.
The deletion of any member because of a move is recorded in your ISPF log data
set, if allocated.
When you complete the panel and press Enter, ISPF displays another panel that is
determined by the option you selected. This panel allows you to specify the “To”
or “Target” data set or controlled library. Both the “From” and “To” or “Target”
data sets must already exist. If the ″Target″ data set does not exist the user is
prompted to see if the data set should be allocated. Choices are to allocate the
″Target″ data set using the characteristics of the ″From″ data set as a model, or to
allocate the new data set by specifying the characteristics for it. This function can
be suppressed through the ISPF Configuration table. If it is suppressed, an allocate
request for a nonexistent data set fails.
If you select C or CP, the panel shown in Figure 103 on page 145 is displayed. This
panel allows you to specify the “To” data set—the library or data set name that
you want the copied data to be stored under.
C — Copy Data Set or Member(s): Use option C to copy a data set. You can
specify either a DASD-resident sequential or partitioned data set for both the
“From” or “To” data sets. The “From” data set is not deleted.
CP — Copy and Print: Use this option as you would use option C, except source
listings are recorded in the ISPF list data set, as follows:
v If the “To” data set is partitioned, a listing of each new or replaced member is
recorded.
v If the “To” data set is sequential, a listing of its complete contents is recorded.
All the fields on the Move/Copy Utility “To” panels for copying data sets are
explained in the Libraries and Data Sets chapter of the ISPF User’s Guide Volume I,
except the following general Options and To Data Set Options:
Replace like-named PDS members
Select this option to allow replacement of a member in the “To” data set
with a like-named member in the “From” data set.
Process member aliases
Select this option to allow the primary member and all alias members to be
copied together.
Sequential Disposition
If the “To” data set is sequential, enter:
1 To add the “From” data set to the end of the “To” data set (Mod).
2 To replace the “To” data set’s entire contents with the contents of
the “From” data set (Old).
If you select M or MP, the panel shown in Figure 104 on page 147 is displayed.
This panel allows you to specify the “To” data set—the library or data set name
that you want the moved data stored under.
M — Move Data Set or Member(s): Use option M to move a data set. You can
specify either a DASD-resident sequential or partitioned data set for both the
“From” or “To” data sets.
Option M causes data sets to be deleted after they have been successfully moved
to the “To” data set, as follows:
v If the “From” data set is partitioned, the selected members are deleted from it.
v If the “From” data set is sequential, the complete “From” data set is deleted.
MP — Move and Print: Same as option M, except source listings are recorded in
the ISPF list data set, as follows:
v If the “To” data set is partitioned, a listing of each new or replaced member is
recorded.
v If the “To” data set is sequential, a listing of its complete contents is recorded.
All the fields on the Move/Copy Utility “To” panels for moving data sets are
explained in the Libraries and Data Sets chapter of the ISPF User’s Guide Volume I,
except the following general Options and To Data Set Options:
v Replace like-named PDS members.
v Process member aliases
v Sequential Disposition
v Pack Option
v SCLM Settings
See “C and CP — Copying Data Sets” on page 144 for descriptions of these fields.
- When a PDSE has been specified in the ″From″ data set concatenation or as
the ″To″ data set.
– If the WHEN_TO_USE_IEBCOPY setting is 1, IEBCOPY is always used to
copy load modules.
– If the WHEN_TO_USE_IEBCOPY setting is 2, IEBCOPY is only used when a
PDSE has been specified in the ″From″ data set concatenation or as the ″To″
data set.
– If the WHEN_TO_USE_IEBCOPY setting (as described above) indicates that
IEBCOPY should be used, the following rules apply when determining
whether to reblock or not:
- When the USE_IEBCOPY_COPY_OR_COPYMOD_OPTION setting is 1:
v If the “To” and “From” block sizes are the same, no reblocking occurs.
ISPF uses IEBCOPY COPY.
v If the “To” block size is larger than the “From” block size, no reblocking
occurs. ISPF uses IEBCOPY COPY.
v If the “To” block size is smaller than the “From” block size, reblocking
occurs. ISPF uses IEBCOPY COPYMOD.
- When the USE_IEBCOPY_COPY_OR_COPYMOD_OPTION setting is 2:
v If the “To” and “From” block sizes are the same, no reblocking occurs.
ISPF uses IEBCOPY COPY.
v If the “To” block size is larger than the “From” block size, reblocking
occurs. ISPF uses IEBCOPY COPYMOD.
v If the “To” block size is smaller than the “From” block size, reblocking
occurs. ISPF uses IEBCOPY COPYMOD.
– When the USE_IEBCOPY_COPY_OR_COPYMOD_OPTION setting is 3:
- Reblocking occurs. ISPF uses IEBCOPY COPYMOD.
v If IEBCOPY is used to process the copy, ISPF allocates the following:
The SYSPRINT data set is deleted when the copy ends successfully. If errors are
encountered, it is kept to help you diagnose errors. SYSIN, SYSUT3, and SYSUT4
are temporary data sets that use VIO if available, and are freed upon completion
of the copy. All allocations use the value of ISPF Configuration table keyword
PDF_DEFAULT_UNIT as the unit. The sizes for the SYSUT3 and SYSUT4 data
sets are calculated dynamically, based on the number of members to be copied.
If this is not sufficient for your move/copy request, these DDNAMES can be
preallocated. If they are preallocated, ISPF does not free them when the copy is
finished.
– Copying to the same data set is not supported when aliases are automatically
selected, as this would result in the from and to member name being the
same.
v If ISPF is not using IEBCOPY and the “Process member aliases” option has not
been selected (ie in NOALIAS mode):
– After the move or copy is successfully completed for the main member or
members, then the alias entry or entries can be copied.
– From a member list:
- When the main member or members are selected first, are not renamed,
and are successfully moved or copied, then the alias entry or entries can be
copied if they are selected without leaving the member list.
- If the target data set is a PDSE, alias entries cannot be copied.
v If IEBCOPY is being used and NOALIAS is in effect:
– The method described above for copying when not using IEBCOPY will also
work when using IEBCOPY. In addition, if all main members and aliases are
selected at the same time they are processed by the same invocation of
IEBCOPY and are copied correctly.
– If the target data set is a PDSE, alias entries must be selected and processed
together with the main member.
In all other cases for move and copy where NOALIAS is in effect, you can select
alias names, but they are not preserved as aliases in the “To” data set. That is, the
members to which they refer are moved or copied, and the alias entries are stored
in the “To” data set with the alias flags turned off.
Note: When you use a referral list from within the Data Set List
Utility, the following functions are performed before the
referral list is processed:
v The quotes are removed from the data set name.
v The value in ZPREFIX is added preceding the non-quoted
data set name if the first qualifier is not ZPREFIX.
v The member name is removed.
RefMode For information about referral list modes, see the Personal List
Modes section in the Using Personal Data Set Lists and Library
Lists chapter of the ISPF User’s Guide Volume I.
Utilities For more information, see the section on the Utilities Action Bar
Choice in the ISPF User Interface chapter of the ISPF User’s Guide
Volume I.
Help The Help pull-down offers you the following choices:
1 General
2 Displaying a Data Set list
3 Printing a Data Set list
4 Display/Print VTOC information
5 Appendices
6 Index
Dsname Level
This field is used to specify the level or levels of any data set that you want ISPF
to list or print for you. An optional installation exit, called the data set list
(DSLIST) exit, can control whether a data set name should appear in the list. Refer
to ISPF Planning and Customizing for more information about this exit.
When you specify the Dsname Level, you are defining the level qualifiers for the
data set names to be included in the list. Therefore, in Figure 105 on page 150, the
value USERID represents the first level of a data set name. For example, an ISPF
library has a three-level name: project, group, and type.
ISPF retains the information you put in this field and displays it the next time you
use this panel.
Except for the first level, you can specify the level qualifiers fully, partially, or use
defaults. Do not enclose the value in the Dsname Level field in quotes.
Asterisks and percent signs may be used to filter the list of data sets that is
displayed. For ICF catalog lists and volume lists, asterisks and percent signs may
be used in the high-level qualifier. Asterisks may be used anywhere in a qualifier,
not just in the first and last positions. However, one qualifier must be at least
partially qualified.
A single asterisk by itself indicates that at least one qualifier is needed to occupy
that position. A single asterisk within a qualifier indicates that zero or more
characters can occupy that position. A double asterisk by itself indicates that zero
or more qualifiers can occupy that position. A double asterisk is invalid within a
qualifier.
In this example, all data set names with SYS1 as the first qualifier and at least one
other qualifier will be listed.
SYS1.*
In this example, all data set names with SYS1 as the first qualifier will be listed.
SYS1 or SYS1.**
In this example, all data set names that have a qualifier of CLIST and are in
catalogs that you have authority to will be listed. A VTOC list will contain all data
set names that have a qualifier of CLIST.
**.CLIST
Notes:
1. If you enter a high-level qualifier of ’*’ or ’**’, ISPF displays a pop-up window
to warn you that the search will be for all catalogs on the system and will take
time. If there are many catalogs, this search could take a considerable amount
of time. You can press Enter to continue the search, or you can enter Cancel or
End from the pop-up window to cancel the search. Be aware that if you have
mount authority, a catalog search with ’*’ or ’**’ as the high-level qualifier can
require that volumes be mounted for the catalogs to be searched.
2. The ISPF Configuration table contains a selectable option, named
DISALLOW_WILDCARDS_IN_HLQ, to disallow the use of the ’*’ or ’%’ in the
high-level qualifier.
A single percent sign indicates that any one single alphanumeric or national
character can occupy that position. One to eight percent signs can be specified in
each qualifier. The following example is valid for Dsname Level:
AAA%*.B*%%%B.C
In this example, the list will contain all data sets that start with AAA and one or
more other characters, have a second qualifier that starts and ends with B and has
at least three other characters between the B’s, and have a third qualifier of ’C’.
The list will contain entries from catalogs that you have authority to. A VTOC list
will contain entries that match the above characteristics.
| In the following example, the list will contain all data sets that start with SYS and
| one other character, such as SYS1 or SYS2.
| SYS%
| If you enter a SYS% alias for a SYS1 data set as the Dsname Level (for example,
| SYSP as a single qualifier), you see SYSP as an ALIAS because this single qualifier
| is an alias for SYS1. The data set names pointed to by a SYS% alias can be
| displayed in a data set list by entering any of the following:
| v a Dsname Level of SYS1 and a volume
| v a Dsname Level of SYS%
| v a Dsname Level of the fully qualified data set name (such as SYSP.PARMLIB)
PRO**CT is not valid as a data set name level because a double asterisk (**) is not
valid in the middle of a qualifier.
Alias names that match the specified Dsname Level will be displayed as the alias
name itself. The volume field for all alias names will contain the characters
’*ALIAS’ to indicate this. Real names that match the Dsname Level will also be
displayed.
If you enter ISPFTEST as a Dsname Level and you have real data set names that
start with ISPFTEST and aliases for those real names that start with ISPFTEST, you
would see a list of this format:
ISPFTEST.BASE.CLIST TSOPK1
ISPFTEST.BASE.CLIST.ALIAS *ALIAS
ISPFTEST.BASE.SOURCE TSOPK1
ISPFTEST.BASE.SOURCE.ALIAS *ALIAS
A VSAM cluster entry is flagged in the volume field as ’*VSAM*’. A VSAM path
entry is flagged in the volume field as ’*PATH*’. A VSAM alternate index entry is
flagged in the volume field as ’*AIX*’.
Notes:
1. A catalog search may result in the DSLIST containing duplicate names. This can
occur when the definition of usercatalog aliases results in multiple catalogs
being searched when the data set list is built. Line commands against duplicate
data sets in the DSLIST are supported. Selecting the ″Display Catalog Name″
option will display the name of the catalog associated with each data set on the
Total view. This can identify where duplicate data set names where found. The
existence of duplicates may be inconsistent when changing the DSLEVEL
qualifiers. For example, SYS1.PARM.* may have different results than
SYS1.PAR*. Duplicate entries may or may not display in a consistent manner,
however the DSLIST will always be complete, with no omissions.
2. If a VSAM cluster matches the Dsname Level, all parts of the cluster are listed
even if the data and index portions do not match the Dsname Level.
When a multicluster (key-range) data portion of a VSAM cluster is displayed
on a catalog list, no information is shown except for the volume and device.
The information comes from the VTOC and the catalog name does not match
the VTOC name. When using a VTOC list the information is displayed.
Volume Serial
Use this field to specify the volume serial whose VTOC is to be used by ISPF to
display or print a list of data set names or VTOC information. ISPF retains the
information you put in this field and displays it the next time you use this panel.
If you want to display a list of only the data sets that reside on a particular
volume, leave the Dsname Level field blank and enter the volume serial in the
Volume field.
You can enter a single volume name or a generic volume name to list data sets
from more than one volume. The volume name can be partially specified using
asterisks as global volume name characters and percent signs as placeholders in
the volume name. A single asterisk within a volume name indicates that zero or
more characters can occupy that position. A single percent sign indicates that any
one alphanumeric or national character can occupy that position. Examples follow.
* Lists data set names matching the Dsname Level from all volumes
PRM* Lists names from all volumes beginning with ’PRM’
M%C*
Lists names from volumes beginning with ’M’, followed by any single
character, a ’C’, and any three other characters
Notes:
1. Specifying a single asterisk as a volume name will require more time to display
of print the VTOC list.
2. A generic volume name can not be used to display VTOC information.
Initial View
Use this field to tell ISPF which view of the data set list you would like to see.
ISPF retains the information you put in this field and displays it the next time you
use this panel.
All the scroll commands are available from these displays and function normally,
except for the LEFT and RIGHT commands. These commands switch from one
view to another, because the panels used to show the different views are
connected, as if they formed a ring. Each time you enter the RIGHT command,
another view is displayed in the sequence shown in Figure 106, starting from the
current view. Each time you enter the LEFT command, another view is displayed
in reverse sequence.
If you enter the RIGHT command with the Total view in the sequence displayed,
ISPF displays the Volume view. If you enter the LEFT command with the Volume
view displayed, ISPF displays the Total view. The available views are:
1. Volume The Volume view shows a data set list that contains data set names
and the volumes on which they reside. Figure 108 on page 157
shows a typical data set list display using the Volume view.
2. Space The Space view shows a data set list that contains data set names,
tracks, percentages used, extents, and devices. Figure 109 on page
159 shows a typical data set list display using the Space view.
3. Attrib The Attributes view shows a data set list that contains data set
names, data set organizations, record formats, logical record
lengths, and block sizes. Figure 110 on page 159 shows a typical
data set list display using the Attributes view.
Note: For each of the above, the list is sorted by data set name.
See the list under Figure 111 on page 160 for descriptions of
the fields shown on this panel.
4. Total The Total view shows a data set list that contains all the
information displayed by the Volume, Space, and Attributes views,
plus the created, expired, and referred dates. The list is sorted by
data set name and has two lines per data set. Figure 111 on page
160 shows a typical data set list display using the Total view. The
catalog name can also be displayed if the Display Catalog Name
option is selected and no value is entered into the Volume Serial
field. If the ″Display Catalog Name″ option is selected, three lines
per data set are displayed. Figure 112 on page 160 shows a typical
data set list display using the Total view with the Catalog name.
See the list under the figure for descriptions of the fields shown on
this panel.
Confirm Data Set Delete
This field controls whether the Confirm Delete panel appears when
you are using the D (delete data set) line command from the
displayed data set list or the TSO DELETE command. Use a slash
to select this option.
If you select this option, ISPF displays the Confirm Delete panel
(Figure 92 on page 133), giving you an opportunity to change your
mind and keep the data set. If you try to delete an unexpired data
set, the Confirm Purge panel (Figure 93 on page 134) is displayed
following the Confirm Delete panel. Follow the directions on the
panel to either confirm or cancel the data set purge.
Attention:
If you deselect the option and the data set is deleted, it cannot be
retrieved.
Note: If a plus displays after the volume serial (for example, HSM020+) on a list
obtained from the catalog, the data set spans multiple volumes. Information
displayed about that data set by selecting Information or Short Information
or by using the Space or Total view will represent the total amounts across
all used volumes.
obtained from the VTOC of that volume. When the multivolume data set is
selected for information or for short information, the space information will
be for all volumes that the data set spans.
Data Set List Panel Action Bar: The Data Set List panel action bar choices
function as follows:
Menu For more information, see the section on the Menu Action Bar Choice in
the ISPF User Interface chapter of the ISPF User’s Guide Volume I.
Options
The Options pull-down offers the following choices:
DSLIST Settings
The settings to control the behavior of the data set list display.
Options are:
v Display Edit/View entry panel
Note: The APPEND is based on the selected personal data set list.
If an entry in the list is not quoted, your TSO prefix is
added as the first level of the data set name. If the entry
contains a member, the member is ignored. Duplicate
personal list entries are ignored. If the entry contains a
volume and “Include volume on retrieve” is selected on the
Referral List Settings panel, a VTOC search is used instead
of the catalog. A catalog search is recommended for best
performance. A volume should be used only if the data set
is not cataloged.
Note: The current setting will be shown as an unavailable choice; that is, it
will display in blue (the default) with an asterisk as the first digit of
the selection number (if you are running in GUI mode, the choice
will be grayed).
1 Volume Changes the display to the Volume view, as shown in
Figure 108 on page 157.
2 Space Changes the display to the Space view.
-------------------------------------------------------------------------------
MYPROJ.DEV.LOAD MVS8WF
15 6 1 3390 PO U 0 27998 2002/07/08 ***None*** ***None***
-------------------------------------------------------------------------------
MYPROJ.DEV.PANELS MVS8WJ
15 6 1 3390 PO FB 80 27920 2002/07/08 ***None*** 2002/07/31
-------------------------------------------------------------------------------
MYPROJ.DEV.SOURCE MVS8WF
15 6 1 3390 PO FB 80 27920 2002/07/08 ***None*** 2002/08/05
-------------------------------------------------------------------------------
MYPROJ.DEV.SOURCE2 MVS8WH+
Command ===> Scroll ===> PAGE
F1=Help F2=Split F3=Exit F5=Rfind F7=Up F8=Down F9=Swap
F10=Left F11=Right F12=Cancel
CATALOG.MASTER.S13L8C
-------------------------------------------------------------------------------
MYPROJ.DEV.LOAD MVS8WF
15 6 1 3390 PO U 0 27998 2002/07/08 ***None*** ***None***
CATALOG.UCATAPC
-------------------------------------------------------------------------------
MYPROJ.DEV.PANELS MVS8WJ
15 6 1 3390 PO FB 80 27920 2002/07/08 ***None*** 2002/07/31
CATALOG.UCATAPC
-------------------------------------------------------------------------------
Command ===> Scroll ===> PAGE
F1=Help F2=Split F3=Exit F5=Rfind F7=Up F8=Down F9=Swap
F10=Left F11=Right F12=Cancel
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 112. Data Set List - Total View with Catalog Name (ISRUDSL0)
You can sort the views by focusing on the following fields. These choices
are also available on the View pull-down:
5 By name
6 By Message
7 By Volume
8 By Dsorg
9 By Recfm
10 By Lrecl
11 By Blksz
12 By Tracks
13 By Percent Used
14 By Extents
15 By Device
16 By Creation date
17 By Expiration date
18 By Referenced date
19 By Volume indicator
20 By Catalog.
Utilities
For more information, see the section on the Utilities Action Bar Choice in
the ISPF User Interface chapter of the ISPF User’s Guide Volume I.
Compilers
The Compilers pull-down offers you the following choices:
1 Foreground Compilers. Displays the Foreground Selection Panel.
2 Background Compilers. Displays the Batch Selection Panel.
3 ISPPREP Panel Utility Displays the Preprocessed Panel Utility
panel.
4 DTL Compiler Displays the ISPF Dialog Tag Language Conversion
Utility panel.
Help The Help pull-down offers you the following choices:
1 General
2 Description of ISPF-supplied line commands
3 Using the ″/″ character to represent a quoted Data Set name
4 Format of the displayed list
5 Available primary commands when the list is displayed
6 Appendices
7 Index
Data Set List Panel Fields: The following fields can appear on the data set list
panels. The fields displayed will vary depending on the view that you select.
Command
Field used to enter a line command, TSO command, CLIST, or REXX EXEC
when displaying a data set list. See “Data Set List Utility Line Commands”
on page 169 for more information.
Name Data set name, as in the VTOC or catalog.
Message
This field is initially blank. However, after you carry out an operation on a
data set using one of the built-in line commands listed on the Data Set List
Utility panel, a message appears in this field showing the last function
used on that data set. The line commands and the messages that appear
when they are used are shown in Table 12.
Table 12. Line Commands and Messages
Line Command Message
B Browsed
C Cataloged
E Edited
where:
XXXXXXXX The command entered
# The return code.
Note: See “Data Set List Utility Line Commands” on page 169 for a
description of the Data Set List Utility line commands.
Volume
Volume serial number.
Multivol
Indicates more than one volume or a migration level in the following
manner:
+ (plus sign)
More than one volume
1 Migrated to disk
2 Migrated to tape
Tracks Number of tracks allocated to the data set.
% Percentage of allocated tracks used, expressed in whole numbers, not
rounded. If any track is used, the minimum percentage is 1. If the data set
is a PDSE, the % refers to the percentage of allocated pages used.
Note: See “F — Free Unused Space” on page 174 for information about
freeing track space manually.
XT Number of extents allocated to the data set.
Device
Device type on which the volume that contains the data set is mounted.
Dsorg One of the following data set organizations. In the definitions of these data
set organizations, unmovable means the data set contains absolute addresses
instead of relative addresses. These data sets are not moved to any other
DASD storage location during read/write operations.
PS Sequential
PS-E Sequential Extended Format
PSU Sequential unmovable
PO Partitioned
POU Partitioned unmovable
PO-E Partitioned extended (PDSE)
DA Direct
DAU Direct unmovable
HSF MVS Hierarchical File System
IS Indexed sequential
ISU Indexed sequential unmovable
VS VSAM
VS-E VSAM Extended Format
blank None of the preceding data set organizations.
Recfm Record format specified when the data set was allocated. See “A —
Allocate New Data Set” on page 121 for more information about record
formats.
Lrecl Logical record length, in bytes, specified when the data set was allocated.
Blksz Block size, in bytes, specified when the data set was allocated.
Blksize
Block size, in bytes, specified when the data set was allocated.
Created
Creation date in the national format.
Expires
Expiration date in the national format, specified when the data set was
allocated. If no expiration date was specified, ***None*** is displayed. If a
″never expire″ date (1999/12/31 or its equivalent) is specified, ***Perm*** is
displayed. See “A — Allocate New Data Set” on page 121 for more
information about expiration dates.
Referred
Date, in the national format, that this data set was last accessed.
Catalog
The name of the catalog in which the data set was located. Only displayed
in the Total view when the Display Catalog Name option is selected and
no value is entered in the Volume Serial field.
Actions You Can Take from the Data Set List Panel: The following sections
describe actions you can take from the Data Set List panel.
Line Commands: Line commands can be entered in the Command field to the left
of the data set names. See “Data Set List Utility Line Commands” on page 169 for
definitions of these line commands.
TSO Commands, CLISTs, and REXX EXECs: Besides the ISPF-supplied line
commands, you can also enter TSO commands, CLISTs, and REXX EXECs that use
a fully-qualified data set name as an operand. You can type over the field
containing the data set name to enter commands that require more space than is
provided in the Command field. ISPF determines the end of the command by
scanning the Command field and the field containing the data set name from right
to left. The first character found that differs from the original is considered to be
the last character of the command. Therefore, it is best to enter a blank after the
last character of your command if it extends into the field containing the data set
name.
TSO commands, CLISTs, and REXX EXECs entered are invoked using the ISPF
SELECT CMD service. Variable names starting with an ampersand (&) are
evaluated by ISPF. If you want the underlying command processor to see the
ampersand you must specify 2 ampersands. For example:
DEF NONVSAM(NAME(/) DEVT(0000) VOLUME(&&SYSR2))
Note: If the TSO command, CLIST, or REXX EXEC issues a return code greater
than or equal to 8, processing stops and an error message is displayed.
Using the Slash ( / ) Character: If a command, CLIST, or REXX EXEC requires the
data set name in a position other than the first operand or if other operands are
needed, you can use the slash ( / ) character to represent the quoted data set
name. If no operands are specified after the command, ISPF uses the name of the
data set being acted on as the command’s first operand.
To specify a member of a partitioned data set, enclose the member name or pattern
in parentheses immediately following the / character. You can use this format with
the V (view data set), B (browse data set), D (delete data set), E (edit data set), and
M (display member list) line commands. For information about these line
commands, see “Data Set List Utility Line Commands” on page 169.
You may find it helpful to call the SHOWCMD primary command before using the
slash ( / ) for the first time. After you call SHOWCMD, a special Data Set List
Utility panel appears each time you enter a line command, TSO command, CLIST,
or REXX EXEC on a data set list display. The panel shows you the command you
entered and how ISPF expanded, and thus interpreted, that command. See
“SHOWCMD Command” on page 180 for more information about and an example
of the SHOWCMD primary command.
The following rules apply to substituting the slash ( / ) character for a data set
name. Each rule is followed by one or more examples that prove the rule by using
either a CLIST or a line command.
In each example, the data set being acted on is USER.TEST.DATA, which always
appears, either completely or partially, in uppercase. However, the CLIST or line
The following example shows how rule 5 on page 165 would apply if you
typed %clist5 member1(abc). The purpose of this example is to show that the
results do not change if the CLIST operand contains a member name enclosed
in parentheses.
(Original) USER.TEST.DATA
(As typed) %clist5 member1(abc)ATA
(After) %CLIST5 MEMBER1(ABC) ’USER.TEST.DATA’
A TSO command, CLIST, or REXX EXEC can set the following variables and place
them in the shared pool to communicate with the Data Set List utility (option 3.4).
Table 14. TSO Command/CLIST/REXX EXEC Variables (Input)
Length in
Variable Name Description Characters
ZDLNDSN New data set name to appear in list 44
ZDLMSG Message to appear in list 16
ZDLREF Refresh data set information; Y | N 1
Note: All data set lists are formatted the same when they are printed.
Therefore, values entered in the Initial View field have no effect when
you use option P.
2. Press Enter to print the data set list. The data set list is stored in the ISPF list
data set.
Note: The Dsname Level field is not applicable for the V or PV command.
Only the Volume field is relevant.
Track values do not include the remaining alternate tracks for the volume. The free
space track values are the number of tracks for the free cylinders plus any
additional free tracks.
Note: The Dsname Level field is not applicable for the PV or V command.
Only the Volume field is relevant.
Line commands that are valid for aliases may be used with any alias data sets that
are listed. Uncatalog, delete, and rename commands are not valid for alias data
sets. A line command such as ’B’ for browse or ’I’ for information will display the
real name of the data set.
The Command field and the field containing the data set name fields make up a
single point-and-shoot field. If you enter a slash in the Command field or if you
select any part of the combined point-and-shoot field, the Data Set List Actions
pop-up shown in Figure 114 is displayed so that you can select the command you
want to use.
Note: If a CLIST, REXX EXEC, or program is issued against a data set, ISPF
gathers information on the data set and makes it available through dialog
variables. See Table 13 on page 166 for the list of those variables. If the data
set being processed is an unmounted HFS, a temporary mount is issued,
updating the last referenced date of the HFS.
Note: Multivolume data sets do not support the Volume Serial field for the Edit
command.
If you select a library or other partitioned data set, an Edit member list is
displayed. For more information about using member selection lists, see the
Libraries and Data Sets chapter of the ISPF User’s Guide Volume I.
The E line command uses the values from a prompt panel to specify items
including the initial macro, profile name, panel name, format, mixed mode, and
workstation editing. These values are stored in the profile and are used on
subsequent edits.
To change these values, use the “DSLIST settings” panel on the data set list
Options pull-down. Check both the “E,V,B enhanced member list” and the
“Display Edit/View entry panel” options. The prompt panel is always shown
when you edit a sequential file, or when you directly edit a member of a
partitioned data set. When you are using a member list you can force the display
of the panel by placing a slash mark (/) in the Prompt field next to the member
you select.
Note: Multivolume data sets do not support the Volume Serial field for the View
command.
If you select a library or other partitioned data set, an Edit member list is
displayed. For more information about using member selection lists, see the
Libraries and Data Sets chapter of the ISPF User’s Guide Volume I.
Note: From a catalog list, multivolume data sets do not support the Volume Serial
field for the Browse command.
From the member list, you can use the same primary commands and line
commands that are valid for Library utility (option 3.1) member selection lists. See
the sections on Using Member Selection Lists and Library and Data Set List Utility
Line Commands in the Libraries and Data Sets chapter of the ISPF User’s Guide
Volume I.
Notes:
1. From a VTOC list, you can browse a single volume of a multivolume non-SMS
data set.
2. You can chain the line commands; that is, you can select multiple members
from a member list for various processing tasks. Use the CANCEL command
(from a View, Browse, or Edit session) to break the chain and return to the
member list.
You can also enter TSO commands, CLISTs, or REXX EXECs in the Line Command
field. If you enter a line command other than B (browse), D (delete), E (edit), R
(rename), C (copy), M (move), G (reset), J (submit), or P (print), ISPF interprets it
as a TSO command, CLIST, or REXX EXEC.
The command is selected with the quoted, fully-qualified data set name and
member added to it, such as:
COMMAND ’DSN(MEMBER)’
See “TSO Commands, CLISTs, and REXX EXECs” on page 164 for more
information.
Note: If the TSO command, CLIST, or REXX EXEC issues a return code greater
than or equal to 8, processing stops and an error message is displayed.
Figure 115 shows an example of a member list with statistics and an expanded line
command field.
Figure 115. Member List Display - Expanded Line Command Field (ISRUDSM)
Figure 116 on page 173 shows load module library statistics with an expanded line
command field.
Figure 116. Load Module Library Display - Expanded Line Command Field (ISRUDSM)
Note: Delete is not allowed for multivolume data sets from a VTOC list.
If you select the Confirm Delete option on the Data Set List Utility panel, the
Confirm Delete panel (Figure 92 on page 133) is displayed to allow you to continue
or cancel the operation. Note that Confirm Delete is forced on when deleting
members by pattern. If you are trying to delete an unexpired data set, the Confirm
Purge panel (Figure 93 on page 134) is also displayed.
When you delete a data set the volume name is compared to the volume name in
the configuration table. If the names match, the command specified in the
configuration table is used in place of the ISPF delete processing. This allows you
to delete migrated data sets without first causing them to be recalled.
Note: Rename is not allowed for multivolume data sets from a VTOC list.
See “R — Rename Entire Data Set” on page 129 and “Renaming Managed Data
Sets” on page 130 for more information.
utility (option 3.2). See “I — Data Set Information” on page 111 and “Information
for Managed Data Sets” on page 113 for more information.
Note: For multivolume data sets, options I and S display current allocation and
utilization values that represent totals from all volumes used.
S — Information (Short)
For the S command, the processing is the same as if you had selected option S
from the Library utility (option 3.1) or the Data Set utility (option 3.2). See “S —
Short Data Set Information” on page 115 and “Short Information for Managed Data
Sets” on page 116 for more information.
Note: The Print command is not allowed for multivolume data sets from a VTOC
list.
The Z command calls either the IEBCOPY utility or the compress request exit
routine. Refer to ISPF Planning and Customizing for more information.
However, if the data set has been allocated with CYLS (cylinders) specified as the
space units, only the tracks beyond the last cylinder used are freed. For example, if
a data set occupies 1.2 of 3 allocated cylinders, the F command frees all tracks
beyond the last used cylinder, leaving 2 cylinders allocated.
Note: The Print command is not allowed for multivolume data sets from a VTOC
list.
RS — Reset
For the RESET command, a panel is displayed that prompts you to reset or delete
ISPF statistics, and to enter a new user ID, version number, or modification level.
MO — Move
For the MOVE command, a panel is displayed that prompts you for a library or
data set name for the to data set.
Note: How aliases are handled by the MO and CO line commands depends on
how the Process member aliases option is set. For more information see
“Moving or Copying Alias Entries” on page 148.
CO — Copy
For the COPY command, a panel is displayed that prompts you for a library or
data set name for the to data set.
Note: How aliases are handled by the MO and CO line commands depends on
how the Process member aliases option is set. For more information see
“Moving or Copying Alias Entries” on page 148.
RA — RefAdd
For the REFADD command, you are provided with an interface to referral lists,
where you can add a data set and a volume to a Personal Data Set List.
3. Press Enter.
This procedure saves keystrokes because you type the CLIST name only once and
you press Enter only once.
The following sections describe these commands, which are shown in alphabetical
order.
APPEND Command
The APPEND primary command appends additional data sets an existing
displayed DSLIST. Use the following format:
You can use the APPEND command with no parameters to get a list of your
personal data sets. Then select the one you want to append to the current list.
If you give a list name with the command, the list given is appended.
By specifying DSname level as a parameter, you can use the resulting list to select
which list to append to the current one. For example, entering APPEND Userid.C*
gives you a list of all personal lists that begin with C as the second-level identifier.
Then you can select the one to append.
By specifying DSname level in quotes, data sets beginning with the DSname level
are appended to the data set list.
CONFIRM Command
The CONFIRM primary command controls display of the Confirm Delete panel.
Use the following format:
You can use the following operands with the CONFIRM command:
ON Tells ISPF to display the Confirm Delete panel when you enter the D
(delete data set) line command or TSO DELETE command. This is the
default setting.
For example, the following command would tell ISPF not to display the Confirm
Delete panel:
CONFIRM OFF
EXCLUDE Command
The EXCLUDE primary command excludes data sets from a list based on a
character string. Use the following format:
You can use the following operands with the EXCLUDE command:
character string
Tells ISPF which data set to exclude from the list.
ALL Tells ISPF to exclude every data set in the list.
NEXT| FIRST | LAST | PREV
Operands that define the starting point, direction, and extent of the lines to
exclude.
PREFIX | CHARS | SUFFIX | WORD
Operands that set the conditions for a character string match.
For example, the following command tells ISPF to exclude a data set that includes
BILBO3 in the name from a list:
EXCLUDE BILBO3
For example, the following command would tell ISPF to find all occurrences of the
character string ELSE:
FIND ELSE ALL
The operands X and NX can be used to limit your search to excluded (X) or
unexcluded (NX) data sets.
For more information about the operands used with this command, see
“FIND—Finding Character Strings” on page 92. NEXT and CHARS are the default
operands.
ISPF automatically scrolls to bring the character string to the top of the list. To
repeat the search without reentering the character string, use the RFIND command.
Note: RFIND search starts from the second data set in the list. It is not
cursor-sensitive.
LC Command
The LC primary command invokes the color change utility from the command line
of a data set list display, as shown in Figure 117.
Change one or more of the Data Set List Field Attributes and press Enter
to immediately see the effect. Clearing a field restores defaults.
More: +
Field: Color: Intens: Hilite: Defaults:
Volume . . . . . . BLUE . . . LOW . . . NONE Blue
* Data Set Name . . GREEN . . . LOW . . . NONE Green
Data Set Stats . . TURQ . . . LOW . . . NONE Turquoise
Create,Expire,
Catalog . . . . . YELLOW . . . LOW . . . NONE Yellow
Message . . . . . WHITE . . . LOW . . . NONE White
Tracks,Device . . WHITE . . . LOW . . . NONE White
Marked Data Set . YELLOW . . . HIGH . . . NONE Yellow
* _ Use Point-and-Shoot field attributes on Data Set Name field
--------------------------------- Example ------------------------------------
Command - Enter ’/’ to select action Message Volume
Tracks % XT Device Dsorg Recfm Lrecl Blksz Created Expires Referred
Catalog
------------------------------------------------------------------------------
ISR.V5R5M0.ISRLOAD Browsed HSM001
Command ===> ____________________________________________________ Defaults
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F12=Cancel
Figure 117. Data Set List Color Change Utility Panel (ISRDLCP)
LOCATE Command
The LOCATE primary command scrolls the list of data sets based on the field on
which the data set list is sorted, as described under “SORT Command” on page
181. Use the following format:
LOCATE lparm
You can use the lparm operand with the LOCATE command for either of the
following situations:
v If the list is sorted by data set name, specify a data set name.
v If the list is sorted by another field, specify a value for the field by which the list
is sorted.
For example, for a data set list sorted by volume, you could enter the following:
LOCATE TSOPK1
This command locates the first data set in the list on volume TSOPK1. If the value
is not found, the list is displayed starting with the entry before which the specified
value would have occurred.
MEMBER Command
The MEMBER primary command is used to search for a member name or pattern
in all of the partitioned data sets in the data set list. It can be abbreviated as M or
MEM. The parameters, X, EX, NX, RECALL1, and RECALL2 are optional. X and
EX limit the search to excluded data sets. NX limits the search to non-excluded
data sets. RECALL1 includes data sets migrated to DASD in the search. RECALL2
includes all migrated data sets in the search. Use the following format:
MEMBER string X
[ EX
[ NX
[ RECALL1
[ RECALL2
The data set list is scrolled so that the first data set containing the member or
pattern is at the top of the list. The MEMBER command finds any occurrence of
the specified member name or pattern within a partitioned data set.
REFRESH Command
The REFRESH primary command updates the display of the data set list to
whatever the list’s current state is. For example, after deleting several items on the
list, REFRESH causes the list to be displayed without the deleted items. If you
have appended to the list, REFRESH restores the list to its status before the append
operation.
RESET Command
The RESET primary command unexcludes data sets that were excluded from a list,
and removes any pending line commands and messages from the data set list.
SAVE Command
The SAVE primary command writes the data set list to the ISPF list data set or to a
sequential data set. ISPF writes the data set list in its current sort order. If the
Display Catalog Name option is selected and Volume Serial was not entered, the
catalog name associated with each data set is included in the Data Set List written
to the sequential file. Use the following format:
SAVE [list-id]
where list-id is an optional user-specified qualifier of the data set to which the
member list will be written. ISPF names the data set:
prefix.userid.list-id.DATASETS
where:
prefix
Your data set prefix, as specified in your TSO user profile. If you have no
prefix set, or if your prefix is the same as your user ID, the prefix is omitted
and the data set name will be: userid.list-id.DATASETS.
userid
Your TSO user ID.
The data set is created if it does not exist, or written over if it exists, and has
compatible attributes. If you omit the list-id operand, the list is written to the ISPF
list data set and includes the list headings.
The following command would tell ISPF to write the list to a sequential data set
named either prefix.userid.MY.DATASETS or userid.MY.DATASETS.
SAVE MY
If the sequential data set already exists, ISPF writes over it; if not, ISPF creates it.
ISPF displays a message, if necessary, when you enter a SAVE or SORT primary
command that shows that the data needed to do the function is being retrieved.
The keyboard locks when this message appears and stays locked until the SAVE or
SORT command is completed.
SHOWCMD Command
The SHOWCMD primary command controls the display of line commands and
their operands as they are called. Use the following format:
where:
ON
Tells ISPF to display line commands. This is the default setting.
OFF
Tells ISPF not to display line commands. Though the SHOWCMD default is
ON, SHOWCMD is initially set to OFF.
After you enter SHOWCMD ON, a panel (Figure 118 on page 181) is displayed
each time you enter a line command, TSO command, CLIST, or REXX EXEC on a
data set list display.
On this panel, you see the command as you typed it and then, a few lines down,
you see the command as ISPF interpreted it. Seeing these commands displayed can
be especially useful when you use the slash ( / ) character to substitute for the
data set name because the panel shows the line command after expansion occurs.
Therefore, you can tell immediately whether you need to add operands to the
command.
For example, suppose you have a data set list displayed on the screen and decide
to browse member MEMB1 of data set USER.TEST.DATA. To see how ISPF
interprets the B (browse) line command, type SHOWCMD ON on the Command
line and press Enter. Then, enter the following line command in the Line
Command field to the left of USER.TEST.DATA:
B /(MEMB1)
When you press Enter, the panel shown in Figure 118 on page 181 appears.
Command ===>
F1=Help F2=Split F3=Exit F9=Swap F12=Cancel
F10=Left F11=Right F12=Cancel
Notes:
1. The data set name and commands shown in Figure 118 are for illustrative
purposes only. These values are determined by the command you enter and the
data set acted on by that command.
2. SHOWCMD must be entered from a data set list. It is invalid if you use a line
command, such as M, to display a member list before calling it.
When the panel showing the commands is displayed, you can do one of the
following:
v Press Enter to call the command displayed in the “Command after expansion”
field.
v Change the command displayed in the “Command after expansion” field and
then press Enter to call the changed command.
v Enter the END command to return to the data set list display.
For information about using line commands, TSO commands, CLISTs, REXX
EXECs, and the / character on a data set list display, see “Blank — Display Data
Set List” on page 156.
SORT Command
The SORT primary command sorts the data set list by the specified field. Use the
following format:
where:
field1
The major sort field. If only one operand is used, ISPF treats it as field1. If both
operands are used, ISPF sorts the list by field1 first, then by field2 within field1.
field2
The minor sort field.
For example, to sort a data set list by volume and block size within each volume,
use the following command:
SORT VOLUME BLKSZ
If you do not specify a field, ISPF sorts the list by data set name. The keywords
described in Table 15 tell ISPF by which fields to sort the data set list.
Table 15. Sort Fields for Source Libraries
Field Sequence Description
NAME Ascending Data set name
MESSAGE Ascending Command completion message
VOLUME Ascending Volume serial
DEVICE Ascending Device type
DSORG Ascending Data set organization
RECFM Ascending Record format
LRECL Descending Logical record length
BLKSZ Descending Block size
TRACKS Descending Data set size
%USED Descending Percentage used
XT Descending Extents used
CREATED Descending Creation date
EXPIRES Ascending Expiration date
REFERRED Descending Last accessed data
MVOL Ascending Multivolume or migration level
CATALOG Ascending Catalog Name
PROMPT Descending Data displayed in PROMPT field
Automatic scrolling is performed, if necessary, to bring the major sort field into
view. ISPF displays a message when you enter a SAVE or SORT primary command
that shows that the data needed to do the function is being retrieved. The
keyboard locks when this message appears and stays locked until the SAVE or
SORT command is completed.
SRCHFOR Command
Use the SRCHFOR primary command to search the data sets in the data set list for
one or more strings of data using the SuperC Utility (see Option 3.14). You may
limit the search to excluded or non-excluded data sets, and control whether
migrated data sets are recalled and searched or not. Use the following format:
SRCHFOR string
The string parameter is optional and if specified is used to prefill the first search
string on the subsequent DSLIST Srchfor Options panel.
WORD, SUFFIX, and PREFIX are available operands for search string specification.
Note that the search strings are case sensitive and must match exactly as specified.
Consider the ’Any case’ process option if you want to disregard case.
You can use the C (continuation) operand to specify that both the current and
previous string must be found on the same line to constitute a match. Otherwise,
lines with either string are treated as matching.
Table 16. SRCHFOR Command Search String Examples
Example Search strings: Explanation:
===> ABC Either string ABC or EFG may be found in the search data set.
===> EFG
===> ABC WORD The two strings (ABC and EFG) must be found on the same
===> EFG C line. ABC must be a complete word, while EFG (a continuation
definition) can be part of any word.
===> ABcD prefix The string (ABcD) is detected if the case of each letter matches
and it is a prefix of a word.
===> X’7b00’ The hex string is specified as the search string. The listing must
be browsed with ’HEX ON’.
To start the search, press the Enter key from the DSLIST Srchfor Options panel. To
cancel the request and return to the Data Set List, enter END or CANCEL.
Output is in the listing DSN you specify and in the MESSAGE field in the DSLIST.
Sort on this field to consolidate results.
For information about ISPF Member Statistics, see the Libraries and Data Sets
chapter in the ISPF User’s Guide Volume I.
If you are updating the user ID but not resetting the sequence numbers,
the statistics are updated but the data is not scanned or renumbered.
New Version Number
Enter a number here if you want to change the version number. This field
is required if you do not specify a new user ID when resetting statistics. It
is ignored if you are deleting statistics.
Reset Mod Level
Use a slash to select this option and reset the modification level. Deselect
this option if you do not want to reset the modification level. A new
version number is required to reset the modification level.
Reset Sequence Numbers
Use a slash to select this option and reset the sequence numbers. Deselect
this option if you do not want to reset the sequence numbers. A new
version number is required to reset the sequence numbers. Only standard
(STD) sequence numbers will be reset.
If the data is in packed format, there can be no sequence number
processing. However, statistics for members in packed format can be
created or updated if the sequence numbers are not being reset.
SCLM Settings
The SCLM setting is a bit that ISPF uses to determine what type of edit the
file last had performed upon it.
1 SCLM
This bit is ON to specify that the last edit of this file was under
SCLM control.
2 Non-SCLM
This bit is ON to specify that the last edit of this file was under
control of something other than SCLM.
3 As-is
This bit is ON to specify that this copy operation transfers the
current setting of this file as it already is.
Reset Date/Time
The setting of this field determines whether to reset the Last Modified Date
or Time and the Creation Date of the file.
Reset Number of Lines
The setting of this field determines whether to reset the Current Number
of Lines, the Initial Number of Lines, and the Number of Modified Lines
settings. If this field is set ON, the Current Number of Lines and Initial
Number of Lines settings are set to the actual number of lines of the
member.
The Number of Modified Lines setting is dependent on the Reset Mod
Level and Reset Sequence Numbers fields. If either of those are reset and
the Reset Date/Time field is ON, then the value of the Number of
Modified Lines is set to zero. Otherwise, the Number of Modified Lines
remains as is.
The New Userid field is optional for option R. If you specify a user ID, it is placed
in the ID field of the statistics. If you leave the New Userid field blank and select a
member without statistics, the ID field of the statistics is set to the current user ID.
Either a new user ID or a new version number is required when you use this
option. When you specify a version number, the statistics are created or reset as
follows:
Version Number Set to the specified value.
Modification Level Set to zero if requested; otherwise, unchanged.
Creation Date Set to current date in the national format.
Change Date Set to current date, in the national format, and
time.
Current No. Lines Set to the current number of data records.
Initial No. Lines Set to the current number of data records.
No. Modified Lines Set to zero if the Reset Sequence Numbers field is
selected.
If you have requested updating of the modification level and resetting of the
sequence numbers, the last two digits of each sequence number are set to zeros.
Otherwise, they are not changed.
You can use the Hardcopy utility to print any DASD-resident data set except ISPF
list and log data sets; use the ISPF LIST command to print log and list data sets
during an ISPF session.
An optional print utility exit can be specified by your installation. If this exit is
installed, it may cause the Hardcopy utility’s response to differ from the following
descriptions. Refer to ISPF Planning and Customizing for more information about
the print utility exit.
Another factor that can affect the Hardcopy utility’s performance is whether the
TSO/E Information Center Facility is installed. If the TSO/E Information Center
Facility is installed, your installation can optionally allow ISPF to display a panel
for submitting TSO/E Information Center Facility information with the print
request. See “Using the TSO/E Information Center Facility” on page 190 for more
information.
If the TSO/E Information Center Facility is not installed, the Hardcopy utility first
displays the panel shown in Figure 120.
RefList For information about referral lists, see the chapter on Using
Personal Data Set Lists and Library Lists in the ISPF User’s Guide
Volume I.
Utilities For more information, see the section on the Utilities Action Bar
Choice in the ISPF User Interface chapter of the ISPF User’s Guide
Volume I.
Help The Help pull-down offers the following choices:
1 General
2 Function of the hardcopy utility
3 Selecting a print mode
4 Submitting a background job to print a data set or member
5 Routing a data set to a printer local to your terminal group
6 Printing a data set using TSO/E Information Center
Facility
7 Appendices
8 Index
Note: If you specify a Local Printer ID or writer name and you have
selected the Edit PRINTDS Command option on the ISPF Settings
panel (option 0), ISPF displays the Local Print Command Edit panel
to allow you to intercept and edit the PRINTDS command before it
is processed. For more information on editing the PRINTDS
command, see the Libraries and Data Sets chapter in the ISPF User’s
Guide Volume I.
Local Sysout Class
Used in conjunction with the Local Printer ID or Writer Name. Specifies
the output class to use for output processing.
This is a required field. If you are entering a fully qualified TSO data set name,
you must enclose the name in quotes. If you omit the quotes, the data set prefix
from your TSO user profile is automatically added to the beginning of the data
set name.
3. If the data set is not cataloged, specify the volume serial.
4. If your data set is password protected, type the password in the Data Set
Password field. For more information on data set passwords, see the Libraries
and Data Sets chapter of the ISPF User’s Guide Volume I.
5. Specify either BATCH or LOCAL in the Print Mode field.
6. Specify one of the following:
v If you chose BATCH in the previous step, type a Batch SYSOUT class and
any job statement information you need.
v If you chose LOCAL in the previous step, type the name of a local printer or
writer name in the Local Printer ID field. Job statement information is
ignored.
7. Press Enter.
What happens next depends on your choice in step 5. If you chose BATCH, see
step 7a. If you chose LOCAL, see step 7b on page 190.
a. If you chose BATCH, ISPF generates the JCL and displays the panel shown
in Figure 121, with the message JCL generated in the upper-right corner.
Press Enter. For more information about BATCH printing, see Additional
Batch Printing Information.
v Specify another data set name for printing.
b. If you chose LOCAL, ISPF calls the PRINTDS TSO command processor to
print the data set on the specified local printer.
A message is displayed in the short message area to show that PRINTDS
has accepted the request. At this point, you can:
v Specify another option and press Enter
v Enter the END command
v Enter the CANCEL command
8. If you entered CANCEL or END, ISPF determines the next panel you see as
follows:
v If you entered the Hardcopy utility from the ISPF Primary Option Menu or
through the jump function (=), ISPF displays the ISPF Primary Option Menu.
v If you entered the Hardcopy utility from the Utility Selection Panel, ISPF
returns you to that panel.
Once the JCL for the first job step is generated, the job statement operands are
shown for information aboutly. They are no longer highlighted and you cannot
type over them, since the job statement has already been generated. You can then
select another data set name to cause another job step to be generated.
Hardcopy Utility
Printer location . .
Printer format . . .
Number of copies . .
Command ===>
F1=HELP F2= F3=END F4=DATASETS F5=FIND F6=CHANGE
F9=SWAP F10=LEFT F11=RIGHT F12=SUBMIT
Figure 122. Hardcopy Utility Panel - with the TSO/E Information Center Facility Installed
(ISRUHCPI)
Follow these steps to use the TSO/E Information Center Facility to submit your
print jobs:
1. Choose one of the options listed at the top of the panel and type its code, PK or
PD, in the Option field.
2. Enter a fully qualified data set name and member name.
You must specify at least the low-level qualifier, such as LIST. If you enter your
user prefix as part of the data set name, you must enclose the complete data set
name in quotes. However, if you omit the user prefix and quotes, your user
prefix is automatically added to the beginning of the data set name.
3. If the data set is not cataloged, enter the volume serial.
4. If your data set is password-protected, enter the password in the Data Set
Password field. For more information about data set passwords, see the
Libraries and Data Sets chapter of the ISPF User’s Guide Volume I.
5. You can either leave the Printer location field blank or enter the location ID of
the printer to be used. The location ID is assigned by your installation.
You can also enter a partial location name followed by an asterisk (*).
6. You can either leave the “Printer format” field blank or enter the format ID of
the printer to be used. The format ID is assigned by your installation.
You can also enter a partial format name followed by an asterisk (*). If your
printer location and format entries do not identify a specific printer, a printer
selection list is displayed. From this list, which is similar to a member selection
list, you can select a printer.
7. Specify the number of copies you want.
8. Press Enter.
The values entered in the fields on this panel are passed directly to the TSO/E
Information Center Facility for processing.
When you select option 7 from the Utility Selection Panel, ISPF displays the
Download Data Set to Workstation panel shown in Figure 123.
Menu Help
──────────────────────────────────────────────────────────────────────────────
Download Data Set to Workstation
Option ===>
F1=HELP F2= F3=END F4=DATASETS F5=FIND F6=CHANGE
F9=SWAP F10=LEFT F11=RIGHT F12=SUBMIT
When you select option 1 from the Download Data Set to Workstation panel, ISPF
displays the ISPF Client/Server Component Download panel shown in Figure 124
on page 193.
Download methods
1. FTP (requires workstation FTP server)
2. ISPF C/S (requires workstation connection)
3. Manual
Workstation Type
1. Windows 95/98/2000/NT 3. AIX 5. HP UX
2. OS/2 4. Solaris
Command ===>
F1=HELP F2= F3=END F4=DATASETS F5=FIND F6=CHANGE
F9=SWAP F10=LEFT F11=RIGHT F12=SUBMIT
The Client/Server Component Download panel enables you to choose the download
method and workstation type you want to use to put the WSA installation
program on your desktop.
Workstation type
The workstation agent runs on different workstation platforms and you
must indicate which platform you have, so that you receive the correct
version.
1. Windows 95/98/2000 or NT
2. OS/2
3. AIX
4. Solaris
5. HP UX
Directory to copy file to
Specify a directory on your workstation where you want to store the WSA
installation program. You can specify a full path name or a relative
directory, or leave this field blank. If you leave it blank, the download is
made to your home directory (in the case of FTP downloads) or the current
directory (in the case of client/server downloads). If you specify a relative
directory (one that does not start with a drive letter or slash character) the
directory is relative to the FTP home directory or the client/server current
directory.
Data set to copy file from
The host data set that contains the WSA installation program. This value
varies depending on the naming convention that was used when ISPF was
installed.
Create directory to which the file is to be copied
If you want ISPF to create the directory on your workstation before
copying the WSA installation program, enter a ″/″ in this field.
If you do not already have a workstation connection (with or without GUI display)
established, ISPF displays the ISPF Client/Server Installation Notice panel shown
in Figure 125 on page 195.
┌─────────────────────────────────────────────────────────────────────────┐
─ │ ISPWSD03 Client/Server Installation Notice │
I │ │
│ A workstation connection is required to download a new Client/Server │
1 │ component using workstation agent file transfer services. │
2 │ │
│ Do you wish to start a workstation connection now? │
│ 1. Yes, start workstation connection now and continue with download │
│ 2. No, do not start workstation connection │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ │
│ Command ===> │
O │ F1=Help F2=Split F3=Exit F7=Backward F8=Forward │
│ F9=Swap F12=Cancel │
F └─────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────────────────────────┐
─ │ ISPF Client/Server Component Install Program │ ──
I │ │
│ The ISPF Client/Server Component workstation install program has been │
1 │ copied to your workstation in directory: │
2 │ │
│ C:\TEMP │
│ │
│ in directory: │
│ │
│ End your workstation connection, close the active workstation agent, │
│ and complete the installation by running the install program ISPFINST │
│ on your workstation in the directory specified. The program is a self │
│ extracting executable that will result in additional files being │
│ generated on your workstation. │
│ │
│ Do you wish to end your workstation connection now? │
│ 1. Yes, end workstation connection now │
│ 2. No, do not end workstation connection now │
│ │
│ Command ===> │
O │ F1=HELP F2= F3=END F4=DATASETS F5=FIND │
│ F6=CHANGE F9=SWAP F10=LEFT F11=RIGHT F12=SUBMIT │
F └───────────────────────────────────────────────────────────────────────┘
ISPF Library:
Project . . . MYPROJ
Group . . . . DEV . . . . . . . . .
Type . . . . SOURCE
Member . . . (Blank or pattern for member selection list)
Workstation File:
File Name . . . . .
Use the Download or Upload selections to indicate whether you want to download
host data to the workstation, or upload workstation data to the host. Enter 1 for
“download to workstation”. Enter 2 for “upload from workstation”.
You can transfer data from either PDS or sequential host data sets. The host data
set must exist before attempting a transfer, but a PDS member is created if it does
not already exist. Workstation files need not exist before downloading data from
the host, but the specified directory must be there.
For downloading only, you can specify an asterisk (*) character in the workstation
file name. ISPF substitutes the member name of the data being downloaded for the
*. This enables you to select multiple members from the member list to be
downloaded as separate files.
The “Transfer in Text mode” field determines whether the file transfer is done in
text mode (with ASCII to EBCDIC translation) or in binary mode (without any
translation). When transferring in text Mode, the ispf filexfer service provides a
one-to-one mapping of all 256 code points between the host code page and the
workstation code page. Most other file transfer utilities (for example, ftp) only
provide a one-to-one mapping of displayable characters.
The record formats for the corresponding data sets are FBA, FBM,
and FB, respectively.
The list of job names is displayed on the lower portion of the panel. If the list is
too long to fit on the screen, three asterisks are displayed on the last line of the
screen. You can display the remainder of the list by pressing Enter.
An optional print utility exit can be installed by your system programmer. If this
exit is installed, it may cause the Outlist utility’s response to differ from the
following descriptions. Refer to ISPF Planning and Customizing for more
information about the print utility exit.
Another factor that can affect the performance of the Outlist utility is whether the
TSO/E Information Center Facility is installed. If the TSO/E Information Center
Facility is installed, your installation can optionally allow ISPF to display a panel
for submitting the TSO/E Information Center Facility information with the print
request. See Figure 157 on page 258 for an example of this panel and “Using the
TSO/E Information Center Facility” on page 190 for information about the fields
on this panel.
If the TSO/E Information Center Facility is not installed, the Outlist utility displays
the panel shown in Figure 156 on page 251 when you press Enter. Use this panel to
tell ISPF how and where the job output is to be printed. This option does not
honor multiple copies for output on hold queue. To print multiple copies use
option R.
ISPF uses temporary data sets named prefix.userid.SPFxxx.OUTLIST (if your data
set prefix in your TSO user profile is different from your TSO userid) or
userid.SPFxxx.OUTLIST (if your prefix and userid are the same), where xxx is a
number between 100 and 999.
Attention: If you keep or use all data sets through 999, ISPF resets to 100 and
uses the existing data sets. Also, ISPF can use the data sets that you allocate using
the temporary data set naming convention.
The command table displays the search order of commands for a particular logical
screen. The order is from top to bottom of those commands displayed. The “User
table” and “Site table” fields are blank if no values are set for them in the ISPF
Configuration table, or if values have been set but the tables do not exist in the
“ISPTLIB” concatenation.
You cannot use this utility to change a command table that is currently in use.
Command table ISPCMDS, the system command table, is always in use by the
Dialog Manager component. If you enter ISP in the Application ID field, ISPF
displays the ISPCMDS command table in read-only mode.
While you are using this utility to change a command table, the table cannot be
used for other purposes. For example, you cannot use split screen and select a
function with NEWAPPL(XYZ) if you are changing command table XYZCMDS.
Menu Help
─ ┌─────────────────────────────── Commands ────────────────────────────────┐
I │ ISPUCMA Command Table Utility │
│ │
1 │ Specifications Command table search order │
│ Application ID . . ISR Application table . : ISR │
2 │ Enter "/" to select option User table 1 . . . . : USER │
│ Show description field User table 2 . . . . : │
3 │ User table 3 . . . . : │
4 │ Site table 1 . . . . : SITE │
│ Site table 2 . . . . : │
5 │ Site table 3 . . . . : │
6 │ System table . . . . : ISP │
7 │ │
8 │ If no application ID is specified, the current application ID will be │
9 │ used. The name of the command table to be processed is formed by │
1 │ prefixing the application id to the string ’CMDS’. For example: │
1 │ Application ID . . TST results in a command table name of ’TSTCMDS’. │
1 │ │
1 │ Command ===> │
1 │ F1=Help F2=Split F3=Exit F7=Backward F8=Forward │
O │ F9=Swap F12=Cancel │
└─────────────────────────────────────────────────────────────────────────┘
F10=Actions F12=Cancel
The command table for the named application is displayed on a Command Table
editing panel (Figure 130 on page 202). This panel can be scrolled up and down
using the scroll commands.
Insert (I), delete (D), repeat (R) and edit (E) command entries.
Enter END command to save changes or CANCEL to end without saving.
Verb T Action
SORT 0 SELECT PGM(PQRSORT) PARM(&ZPARM)
PREPARE 4
QUIT 2 ALIAS END
EXPLAIN 4
******************************* Bottom of data ********************************
For a new table, this panel initially contains dummy entries with all fields shown
as underscores. The underscores are pad characters and need not be blanked out.
However, any null entries where at least the verb contains all underscores are
automatically deleted when the table is saved.
that number of times. The lines are processed in the order in which they appear on
the screen. Any line commands or changes that are entered concurrently with the
END command are processed before the table is saved.
D — Deleting Lines
The D command deletes one or n lines (D[n]).
E — Editing Lines
The E command edits one or n lines (E[n]). You can modify the action or
description fields of a line.
I — Inserting Lines
The I command inserts one or n lines (I[n]). The inserted lines contain underscores
(pad characters) in all field positions.
R — Repeating Lines
The R command repeats a line one or n times (R[n]). The repeated lines contain
underscores (pad characters) in the Verb and T (truncation) fields, but the Action
and Description fields are copied from the line on which the R command was
entered.
V — Viewing Lines
The V command views one or n lines (V[n]). You can look at the entire command
entry including the command action and description fields, but you cannot change
them.
The purpose of a format is to structure data from a record into fields, and to define
the order these fields are to be physically displayed on the screen when you are
viewing, browsing, and editing.
When you select this option, a panel is displayed (Figure 131 on page 205) that
allows you to add, copy, delete, or update a format. You can also display the
format list.
Format Name . . .
Note: The Format Utility is provided for support of the IBM 5550 terminal
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Note: All three of these field types can contain extended graphics
characters. CAPS ON processing is not possible because of
context dependencies. Therefore, it is ignored when you are
editing formatted data.
The format definition information applies to both existing records and inserted
records in a data set.
Note: It is recommended that you avoid using STD or COBOL formats with
numbered data. The results can be different from using formats with
unnumbered data. If you must use numbered data, do not define the
columns the sequence numbers will appear in, or define an EBCDIC or
mixed data field for them.
C — Copy Formats
If you specify option C on the Format Specifications panel, the following occurs:
v If you specify both an asterisk (*) in the From Format field and a table name
other than ISRFORM in the From Table field, all formats stored in the “From”
table are copied to ISRFORM.
Note: If you specify a table name in the From Table field, and that table does
not have the same format as ISRFORM, a severe error occurs.
v If you specify both a format name and a “From” format, the format is copied. If
you specified a “From” table (other than ISRFORM), the format is copied from
that table. Otherwise, the format is copied from ISRFORM. The Format
Definition panel for the newly created format, containing the currently defined
fields, is displayed. You can add, delete, and update field definitions. When you
enter the END command, the format definition is stored in ISRFORM under the
format name you specified.
v If you specify a format name but no “From” format, the Copy Format Selection
List panel (Figure 133 on page 208) is displayed.
If you did not specify a “From” table, the formats listed are those stored in
ISRFORM, the default format table. Otherwise, the formats listed are those
stored in the table you specified.
Note: The ISRFORM table is the default location in which all of your
user-defined formats are stored. If you have not yet defined any formats,
the table will be empty and you will receive a ″No formats found″
message.
You can select a format to copy by entering the S line command to the left of
that format name. Other commands you can enter are U (Update), R (Rename),
D (Delete), SELECT (which is similar to S), SORT, and LOCATE. See “Format
Selection List Commands” on page 209 for a description of these commands.
The format is copied, and the Format Definition panel for the newly created
format, containing the currently defined fields, is displayed. You can add, delete,
and update field definitions. When you enter the END command, the format
definition is stored in ISRFORM under the format name you specified on the
Format Specifications panel.
v If you specify neither a format name nor a “From” format, but you do specify a
“From” table (other than ISRFORM), the Copy Format Selection List panel is
displayed. You can select one or more formats to copy by entering the S line
command to the left of the format name(s). Each of these formats is copied
under the same name from the specified “From” table to the ISRFORM table.
Note: If you do not specify option C but specify a name in the From Format field,
the From Format field is ignored.
D — Delete a Format
If you specify option D and a format name on the Format Specifications panel, the
format is deleted.
U — Update a Format
If you specify option U and a format name on the Format Specification panel, the
Format Definition panel containing the currently defined fields is displayed. You
can add, delete, and update field definitions.
Deleting a Format
If you specify the D line command beside a format name, the format is deleted.
LOCATE name
where:
name The name of the format you want to find.
For example, the following command would find a format named FORM03:
LOCATE FORM03
If the format exists, the entry for the specified format name appears as the second
line following the header lines. If the specified name is not found, the existing
format name that would immediately precede the specified name appears as the
first line following the header lines.
Renaming a Format
If you specify the R line command beside a format name, you must also specify its
new name in the Rename field before you press Enter. If you do not, the Enter
required field message appears in the upper-right corner of the screen and the
cursor moves to the Rename field.
where:
NAME
Sort by name.
TIME Sort by time last modified.
For example, the following command would sort a format selection list by time:
SORT TIME
You can specify that multiple operations be done at the same time. However, if
you specify U or S with other line commands, any commands after the first U or S
are ignored.
The SELECT command provides you with another way to specify a format. This
command is entered on the Command line.
SELECT name
where:
name
The name of the format you want to select.
If the format exists, the Format Definition panel containing the currently defined
fields is displayed. You can add, delete, and update field definitions.
If no format exists for that name, a new format is created, and the Format
Definition panel is displayed to allow you to define fields.
The SuperC utility (option 3.12) is a dialog that uses the SuperC program to
compare data sets of unlimited size and record length at the file, line, word, or
byte level. The panel shown in Figure 135 is used to specify the name of a new
data set.
Note: In this context, a new data set is an updated version of a previously created
data set, such as a data set in your private library that has been modified
but has not yet been promoted.
Specify "New" Data Set to be compared, then press the ENTER key.
More: +
Project . . .
Group . . . . . . . . . . . . .
Type . . . .
Member . . . (Blank or pattern for member selection list,
"*" for all members)
Profile DS Name . . .
Data Set Password . . (If New data set password protected)
This panel requires only the names of the input data sets and a foreground or
batch mode setting.
Note: For DBCS searches and compares to function properly, ISPF must be
invoked with the JAPANESE keyword, on a terminal that supports DBCS,
and the MIXED process option must be supplied to SuperC.
2 Overview of SuperC
3 Specifying the ″NEW″ data set
4 Specifying the ″OLD″ data set
5 Member selection
6 Setting batch output parameters
7 Interpreting listings
8 Interpreting return codes
9 Appendices
10 Index
Note: Mixed Mode is not valid for the File or Byte compare.
Bypass Selection List
When a member pattern is entered in the PDS Member List field or the
member name portion of the data set field (such as
MY.DATA.SET(pattern)), selecting this field causes SuperC to process all
members matching that pattern without displaying a member selection list.
Leaving this field blank causes the member list to be displayed.
Execution Mode
The processing mode you want to use when comparing the data sets.
Choose one of the following:
1 Foreground. After the old data set panel and member selection, if
any, are completed, foreground mode compares the new and old
data sets and stores the results in the data set specified in the
Listing DS Name field, which you can browse at the terminal.
2 Batch. After the old data set panel and the member list, if any, are
completed, batch mode causes the display of the SuperC Utility -
Submit Batch Jobs panel, so you can specify job card and print
disposition information or edit the JCL. Then, the batch job is
submitted to compare the new and old data sets. See “Submitting a
SuperC Job in Batch Mode” on page 217 for more information.
Output Mode
The output mode you want to use when displaying the listing file. Choose
one of the following:
1 View. This enables the listing file to be displayed in view mode. All
View functions are enabled in this mode.
2 Browse. This enables the listing file to be displayed in the browse
mode. All Browse functions are enabled in this mode.
When you complete the New Data Set panel and press Enter, ISPF displays the
panel shown in Figure 136. Of the five fields shown at the bottom of the panel
(Volume Serial, Listing DS Name, Data Set Password, Listing Type, and Sequence
Numbers), all except Listing Type may not appear, depending on the mode you
choose (foreground or batch) and the contents of the profile data set. Also, if you
request a member list or specify an asterisk (*) in the Member field on the new
data set panel, ISPF does not display a Member field on the old data set panel.
Note: In this context, an old data set is a base version of a data set, such as a data
set in a production library.
Specify "Old" Data Set to be compared, then press the ENTER key to compare to
"New" Data set . . : MYPROJ.DEV.SOURCE
More: +
Project . . . MYPROJ
Group . . . . TEST . . . . . . . . .
Type . . . . SOURCE
Member . . .
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Specify the name of an old data set. The type of old data set that you can specify
depends on the type of new data set you specified on the previous panel. For
example, you can compare:
v A complete new PDS to a complete old PDS
v A new sequential data set to:
– An old sequential data set
– An old membered PDS
v A new membered PDS to an old sequential data set.
In this context, the term membered PDS refers to a PDS for which a single member
has been specified, such as:
’USERID.TEST.SCRIPT(NEWDATA)’
SuperC treats a membered PDS as a sequential data set because the comparison is
done on a one-to-one basis. However, SuperC cannot compare a sequential data set
to a complete PDS because it cannot compare one data set to more than one
member of another data set.
When you press Enter, ISPF either displays a member selection list or begins the
comparison. All the fields on this panel are explained in the Libraries and Data
Sets chapter of the ISPF User’s Guide Volume I, except the following:
Update DS Name
Tells SuperC the name of the data set that will contain column-oriented
results of the comparison.
Note: This field is not displayed unless your profile data set contains an
update (UPDxxxx) process option.
This data set is normally used as input to post processing programs and
can be specified in addition to the normal listing data set. See the Process
Options selection in “Process Options - Select Process Options” on page
227 for information about the SuperC process options.
If you leave this field blank, SuperC uses the following default name:
prefix.userid.SUPERC.UPDATE
where prefix is your TSO prefix and userid is your user ID. If your prefix
and user ID are identical, only your prefix is used. Also, if you do not have
a prefix, only your user ID is used.
If you enter a fully qualified data set name SuperC uses it as specified.
Otherwise, SuperC only appends your TSO prefix to the front of the data
set name specified. If you run with TSO PROFILE NOPREFIX, SuperC uses
the name as you entered it, which can result in an attempt to catalog the
name in the master catalog.
If you enter the name of a data set that already exists, the contents of that
data set are replaced by the new update output.
If you enter the name of a data set that does not exist, SuperC allocates it
for you. The data set is allocated as a sequential data set unless you enter a
member name after it, in which case it is allocated as a partitioned data
set.
CHNG Lists the differences between the source data sets, plus up
to 10 matching lines before and after the differences. This
listing is a variation of the DELTA listing; the matching
lines before and after help you recognize changed areas of
the source data sets.
LONG Lists all the new data set source lines, plus old data set
deleted lines. Both inserted and deleted lines are flagged.
OVSUM Lists only the overall summary of the comparison.
However, a PDS comparison generates an individual
summary line for each PDS member.
NOLIST Produces no listing output. In foreground mode, only a
message is returned to show the outcome of the compare.
Listing DS Name
The name of the list data set to which SuperC writes the results of the
comparison. However, if you enter NOLIST in the Listing Type field,
SuperC does not create an output listing, so this name is ignored. Also, if
you chose batch mode, this field does not appear on the panel. The SuperC
Utility - Submit Batch Jobs panel is used instead.
If you leave this field blank, SuperC allocates a list data set, using default
data set attributes and the following data set name:
prefix.userid.SUPERC.LIST
where prefix is your TSO prefix and userid is your user ID. If your prefix
and user ID are identical, only your prefix is used. Also, if you do not have
a prefix, only your user ID is used.
If you enter a fully qualified data set name SuperC uses it as specified.
Otherwise, SuperC only appends your TSO prefix to the front of the data
set name specified. If you run with TSO PROFILE NOPREFIX, SuperC uses
the name as you entered it, which can result in an attempt to catalog the
name in the master catalog.
If you enter the name of a data set that already exists, the contents of that
data set are replaced by the new output listing. However, if the data set is
sequential, you can add this listing to the data set instead of replacing it by
including the APNDLST process option in your profile data set.
If you enter the name of a data set that does not exist, SuperC allocates it
for you. The data set is allocated as a sequential data set unless you enter a
member name after it, in which case it is allocated as a partitioned data
set.
Sequence Numbers
A value that tells SuperC whether to exclude sequence number fields from
its comparison of your data sets. This field is not displayed if the compare
type is FILE or BYTE. You can choose one of the following:
blank Exclude Sequence Number fields from the comparison if
the data set is F 80 or V 255 and the compare type is
Line
Enter END command to process selections or CANCEL to leave the member list.
Enter Old member(Oldmem) name if it is different from New member(Newmem) name.
The members displayed in this list are members in the new data set. If the
OLDMEM column is blank, SuperC assumes each member in the new data set is to
be compared with a member of the same name in the old data set.
If you enter a member name in the OLDMEM column, SuperC compares this
member to the one listed beside it in the NEWMEM column.
To compare your selections, enter the END command. If you have not selected any
members, ISPF returns you to the previous panel.
Note: Both the jump function (=) and the RETURN command cause an implied
cancellation of selections before they are carried out.
For more information about member lists, see the Using Member Selection Lists
section of the Libraries and Data Sets chapter of the ISPF User’s Guide Volume I.
//OUTDD DD . . . . .
// . . . . . . . . .
LRECL for the Listing Output will be 133
===>
===>
===>
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F12=Cancel
to produce the output. You can enter any valid SYSOUT parameters. This
field is required if you leave the Option field blank.
If you enter either option 1 or option 2, the “SYSOUT class” field is
ignored. However, for option 2, you can include the SYSOUT= operand in
an OUTDD DD field.
Data Set Name
The name of the listing data set that you want ISPF to store your compare
results in. This data set can be either partitioned or sequential.
The Data Set Name field is required if you use option 1 on this panel. This
field serves the same purpose as the Listing DS Name field, which is used
when running the SuperC utility in foreground mode.
The logical record length (LRECL) of the listing data set is displayed under
the blank OUTDD lines on the SuperC Utility - Submit Batch Jobs panel.
SuperC creates listings with one of four LRECLs:
132 Standard listing for the NOPRTCC process option; printer control
characters are omitted.
133 Standard listing.
202 Wide listing for the NOPRTCC process option; printer control
characters are omitted.
203 Wide listing.
If you leave the Option field blank or enter option 2, the Data Set Name
field is ignored. Therefore, to specify an output data set in either of these
two situations, you must include the DSN= operand in an OUTDD DD
field.
The following rules apply when specifying the name of an existing data
set:
v When you submit JCL for processing, the output listing produced by
that JCL usually replaces the contents of the specified data set, if any
exist. Therefore, be careful when specifying the name of an existing data
set.
You can keep a history of changes by using the APNDLST compare
option when you run the comparison. This compare option adds the
new output listing to the specified sequential data set’s contents instead
of replacing it.
Note: Using the APNDLST process option with a packed output listing
file may cause unpredictable results in the output listing file.
v Use standard TSO data set naming conventions.
The following rules apply when specifying the name of a data set that
does not exist:
v If you include a member name in the data set specification, ISPF
allocates a partitioned data set with suitable attributes for the listing.
v If you do not specify a member name, ISPF allocates a sequential data
set.
//OUTDD DD
Output data definitions that are used to specify additional printer
instructions in job control language (JCL). This field is required if you use
this panel. Otherwise, it is ignored.
The OUTDD DD fields are provided so you can pass to your printer all the
JCL needed to format special types of output that may not be supported by
your installation’s SYSOUT class definitions. The example shown in
Figure 138 on page 217 specifies a wide format for printing on 14 3/4-inch
forms.
The “SYSOUT class” and Data Set Name fields are ignored. If you need to
specify this information, be sure to include it in your OUTDD DD job card.
If you specify a data set name in your OUTDD DD job card, the output
data set is printed and kept. Otherwise, it is printed and deleted. Here are
some examples:
v To specify a SYSOUT class, enter:
//OUTDD DD SYSOUT=X
where X is the SYSOUT class, such as A, B, or C.
v To specify a data set name, enter:
//OUTDD DD DSN=fully.qualified.name
// DISP=XXXXX...
where XXXXX... is one of the following:
– For an old data set:
OLD
– For a new sequential data set:
(NEW,CATGL),SPACE=(3325,(50,100),RLSE),UNIT=SYSDA
– For a new partitioned data set
(NEW,CATGL),SPACE=(3325,(50,100,25)),UNIT=SYSDA
– For a sequential data set that will be modified by, instead of replaced
by, the comparison results:
MOD
Note: These three fields are independent of one another. Also, none of them
requires you to provide an OUTDD card in the “Job statement information”
field.
===>
===>
===>
===>
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Figure 139. SuperC Utility - Submit Batch Jobs Panel using NOLIST (ISRSCSB1)
Note: For an introduction to the SuperC and SuperCE utilities (options 3.12 and
3.13), see Appendix A, “SuperC Reference,” on page 393.
The panel shown in Figure 140 on page 221 is the first panel of the SuperCE utility.
It requires only the names of the input data sets, which are entered using standard
TSO naming conventions, such as:
New DS Name . . . . ’USERID.TEST2.SCRIPT’
Note: In this context, a new data set is an updated version of a previously created
data set, such as a data set in your private library that has not yet been
promoted.
New DS Name . . .
Old DS Name . . .
PDS Member List (blank/pattern - member list, * - compare all)
(Leave New/Old DSN "blank" for concatenated-uncataloged-password panel)
Compare Type Listing Type Display Output
2 1. File 2 1. OVSUM 1 1. Yes
2. Line 2. Delta 2. No
3. Word 3. CHNG 3. Cond
4. Byte 4. Long 4. UPD
5. Nolist
Listing DSN . . . . SUPERC.LIST
Process Options . .
Statements Dsn . . .
Update DSN . . . . .
Note: You can also use SELECT process statements in the statements data
set to specify an optional set of PDS members to be searched.
However, the SELECT statement turns off the PDS member list
function.
Compare Type
The type of comparison you want SuperC to perform. Choose one of the
following:
File Compares source data sets for differences, but does not show what
the differences are. This is the simplest and fastest method with the
least amount of processing overhead. For this compare type,
SuperC prepares summary information only and causes all listing
types to produce the same output, except NOLIST, which does not
produce any output listing. A message is returned to notify you of
the compare results.
Line Compares source data sets for line differences. Reformatted lines
(that is, lines with blanks inserted or deleted) are automatically
detected for lines ≤ 256 characters. This compare type is the
default. It is most useful for comparisons of program source code
because it is record-oriented and points out inserted or deleted
lines of code. Lines can be of unlimited size.
Word Compares source data sets for word differences. In this context, a
word is a group of characters that begins and ends with a blank or
other line delimiter. If you use the XWDCMP process option, all
non-alphanumeric characters are considered to be delimiters. Also,
a word cannot be longer than 256 characters.
The Word compare type is most useful for comparing text data
sets. If two data sets contain the same words in the same order,
SuperC considers them to be identical, even if those words are not
on the same lines.
Byte Compares source data sets for byte differences. The output listing
data set consists of a hexadecimal printout with character
equivalents listed on the right. A BYTE compare with a LONG
listing of a data set against itself results in a hexadecimal dump of
that data set. This compare type is most useful for comparing
machine readable data.
Listing Type
The type of listing you want SuperC to create when it compares the data
sets. Listing Type is not a required field in SuperCE. If you do not specify
a listing type, the default is DELTA. See the appendix on Listing Formats
in the ISPF User’s Guide Volume I for sample listings.
OVSUM Lists only the general summary of the comparison.
However, a PDS comparison generates an individual
summary line for each PDS member.
Delta Lists the differences between the source data sets, followed
by the general summary.
CHNG Lists the differences between the source data sets, plus up
to 10 matching lines before and after the differences. This
listing is a variation of the DELTA listing; the matching
lines before and after help you recognize changed areas of
the source data sets.
Long Lists all the new data set source lines, plus old data set
deleted lines. Both inserted and deleted lines are flagged.
Nolist Produces no listing output. In foreground mode, a message
is returned to show the outcome of the comparison.
Listing Dsn
The name of the list data set to which SuperC writes the results of the
comparison. However, if you enter NOLIST in the Listing Type field,
SuperC does not create an output listing, so this name is ignored.
If you leave this field blank, SuperC allocates a list data set, using default
data set attributes and the following data set name:
prefix.userid.SUPERC.LIST
where prefix is your TSO prefix and userid is your user ID. If your prefix
and user ID are identical, only your prefix is used. Also, if you do not have
a prefix, only your user ID is used.
If you enter a fully qualified data set name SuperC uses it as specified.
Otherwise, SuperC only appends your TSO prefix to the front of the data
set name specified. If you run with TSO PROFILE NOPREFIX, SuperC uses
the name as you entered it, which can result in an attempt to catalog the
name in the master catalog.
If you enter the name of a data set that already exists, the contents of that
data set are replaced by the new output listing. However, if the data set is
sequential, you can add this listing to the data set instead of replacing it by
using the APNDLST process option.
If you enter the name of a data set that does not exist, SuperC allocates it
for you. The data set is allocated as a sequential data set unless you enter a
member name after it, in which case it is allocated as a member of a
partitioned data set.
Process Options
Keywords that tell SuperC how to process the compare operation. You can
type these keywords in the Process Options fields or select them from a
panel. See the Process Options selection in “Process Options - Select
Process Options” on page 227 for a table of keywords.
Statements Dsn
The name of the data set that contains your process statements. All
statements data sets must be fixed block with 80-byte records (FB 80). See
the Edit Statements selection in “Process Options - Select Process Options”
on page 227 for more information.
Update Dsn
Tells SuperC the name of the data set that will contain column-oriented
results of the comparison. This data set is normally used as input to post
processing programs and can be specified besides the normal listing data
set.
If you leave this field blank and use an update (UPDxxxx) option, SuperC
uses the following default name:
prefix.userid.SUPERC.UPDATE
where prefix is your TSO prefix and userid is your user ID. If your prefix
and user ID are identical, only your prefix is used. Also, if you do not have
a prefix, only your user ID is used.
If you enter a fully qualified data set name SuperC uses it as specified.
Otherwise, SuperC only appends your TSO prefix to the front of the data
set name specified. If you run with TSO PROFILE NOPREFIX, SuperC uses
the name as you entered it, which can result in an attempt to catalog the
name in the master catalog.
If you enter the name of a data set that already exists, the contents of that
data set are replaced by the new update output. However, if the data set is
sequential, you can add this listing to the data set instead of replacing it by
using the APNDUPD process option.
If you enter the name of a data set that does not exist, SuperC allocates it
for you. The data set is allocated as a sequential data set unless you enter a
member name after it, in which case it is allocated as a partitioned data
set.
Display Output
Tells ISPF whether you want to display the output listing in Browse mode.
Enter one of the following:
Note: The NOLIST listing type overrides Yes, No, and Cond.
Yes Call Browse to display the listing data set after processing the
comparison. This is the default.
No Do not call Browse to display the SuperC listing data set.
Cond Do not call Browse unless SuperC finds differences between the
data sets.
UPD Browse the update data set instead of the list data set. This
parameter is not valid unless you create an update data set by
using one or more of the SuperC process options that begin with
UPD (UPDxxxx).
Bypass Selection List
When a member pattern is entered in the PDS Member List field, selecting
this field causes SuperC to process all members matching that pattern
without displaying a member selection list. Leaving this field blank causes
the member list to be displayed.
Output Mode
The output mode for displaying the listing file. Choose one of the
following:
1 View. This enables the listing file to be displayed in view mode. All
View functions are enabled in this mode.
2 Browse. This enables the listing file to be displayed in the browse
mode. All Browse functions are enabled in this mode.
The panel shown in Figure 141 on page 226 is displayed if you leave the Option
field and the New DS Name or Old DS Name field blank on the SuperCE Utility
panel.
"New" Concatenation
DS1 . . .
DS2 . . .
DS3 . . .
DS4 . . .
"Old" Concatenation
DS1 . . .
DS2 . . .
DS3 . . .
DS4 . . .
For fields DS1 through DS4, both new and old, use normal TSO naming
conventions. You can specify a series of concatenated data sets, an uncataloged or
password-protected data set, or a cataloged data set.
Up to four data sets can be concatenated for both the new and old input data sets.
Make sure the data sets are concatenated in the proper sequence, as follows:
1. If two or more sequential data sets are concatenated as one input data set, the
data set attributes, such as block size, must be identical.
2. PDS concatenations must have the data set with the largest block size as the
first in any concatenation.
3. The SuperCE dialog uses only the first occurrence of a member in the
concatenated series of PDSs as source input for a compare. Any other
occurrences of the member are ignored.
Other partitioned or sequential data sets, volume serials, and data set passwords
are specified as on any other data entry panel. See the Libraries and Data Sets
chapter of the ISPF User’s Guide Volume I for more information.
Note: The Password fields apply only to the other partitioned or sequential data
sets. TSO prompts you if any concatenated data sets are password-protected.
The Password field is only enabled in foreground mode.
The panel shown in Figure 142 on page 227 is displayed if you select option B and
leave the New DS Name or Old DS Name field blank on the SuperCE Utility
panel. You can concatenate up to four data sets that have like attributes. For
example, all must be either sequential or partitioned.
"New" Concatenation
DS1 . . .
DS2 . . .
DS3 . . .
DS4 . . .
"Old" Concatenation
DS1 . . .
DS2 . . .
DS3 . . .
DS4 . . .
This panel is the same as the panel shown in Figure 141 on page 226, except the
Password field is omitted. If your data sets are password protected, compare the
data sets in foreground mode by leaving the Option field on the SuperCE Utility
panel blank.
Word Compare:
ALLMEMS ANYC APNDLST APNDUPD CKPACKL COBOL COVSUM
DPACMT DPADCMT DPBLKCL DPCBCMT DPCPCMT DPFTCMT DPMACMT DPPLCMT DPPSCMT
GWCBL LOCS MIXED NOPRTCC NOSEQ NOSUMS SEQ
UPDCNTL UPDREV UPDREV2 UPDSUMO XWDCMP
Byte Compare:
ALLMEMS APNDLST APNDUPD COVSUM LOCS
NOPRTCC NOSUMS UPDCNTL UPDSUMO
File Compare:
ALLMEMS APNDLST COVSUM FMSTOP
LMCSFC LOCS NOPRTCC
SuperC process options can affect how the input data is processed, and determine
the format and content of the output listing data set. They can also help you save
processing time by avoiding comments and blank lines. A separate group of
options, called update data set options (UPDxxxx), allow you to create update data
sets, examples of which are shown in “Update Data Set Control Output Examples”
on page 480.
All these options can be chosen from the XXXX Compare Process Options panels,
where XXXX is the compare type (FILE, LINE, WORD, or BYTE) that you are
using. The only exception is that the DPxxxx (do not process) options are not
available from a selection panel when you are conducting a WORD comparison.
However, you can type any of them in the Process Options field on the SuperCE
Utility panel. Errors caused by mistyping process options are detected when you
call the SuperCE utility.
For definitions of the SuperC process options, see “SuperC Compare Process
Options” on page 397.
When you select the Edit Statements option from the SuperCE Utility Options
pull-down menu, the SuperCE utility displays the statements data set you specified
in the Statements Dsn field. This data set is always displayed in Edit mode,
allowing you to add, change, or delete SuperC process statements as needed. Only
one process statement can appear on each line of the statements data set.
The size of the Edit window depends on the number of lines your terminal can
display. The sample panel shown in Figure 143 shows how the Edit window
appears on a 24-line display. Examples of some common process statements are
listed below the Edit window so you can easily compose the proper input line.
Examples Explanation
CMPCOLM 5:60 75:90 Compare using two column compare ranges
LSTCOLM 25:90 List columns 25:90 from input
DPLINE ’PAGE ’ Exclude line if "PAGE " found anywhere on line
SELECT MEM1,NMEM2:OMEM2 Compare MEM1 with MEM1 and NMEM2 with OMEM2
CMPLINE NTOP ’MACRO’ Start comparing after string found in new DSN
LNCT 66 Set lines per page to 66
- - - - -
Others: CHNGV CMPBOFS CMPCOLMN CMPCOLMO CMPSECT DPLINEC NCHGT
Command ===> Scroll ===> PAGE
F1=Help F2=Split F3=Exit F5=Rfind F6=Rchange F7=Up
F8=Down F9=Swap F10=Left F11=Right F12=Cancel
The SuperC program validates process statements at run time. Invalid process
statements are not used and are noted at the bottom of the listing. Unless a higher
return code is required by some other condition, a return code of 4 is generated.
See “SuperC Compare Process Statements” on page 407 for process statement
syntax, definitions, and examples.
SuperC profiles are useful for a wide range of users. Beginners can use profiles
created by others as a simple method of running SuperC. Experienced SuperC
users can create profiles for the groups of options they use often so that they do
not have to remember individual process options and statements. Also, profiles
give system programmers a mechanism for setting up complex compare tools that
others can simply call by profile name.
Selecting option A on the SuperCE Utility panel displays the panel shown in
Figure 145. This panel is used to activate and create profiles.
2. Rewrites the profile data set (if the data set exists) or
allocates a new data set before generating the profile.
Activate/Create
Profile DS Name . . .
Option ===>
F1=Help F2=Split F3=Exit F9=Swap F12=Cancel
The following sections describe the options shown at the top of the SuperCE -
Profile Manager panel.
A — Activate: Option A (Activate) restores the contents of the profile data set
specified in the Activate/Create Profile DS Name field. This data set must be
cataloged. When you press Enter, information that was stored in the profile data
set when it was created is displayed in the corresponding fields on the SuperCE
Utility panel. For example, process options stored in the profile appear in the
Process Options fields. At this point, you can make additional changes or choose
another option.
If the profile data set that you specify does not already exist, SuperCE allocates it
for you. Data stored in the profile data set can include:
v The following values taken from the fields on the SuperCE Utility panel. The
abbreviations in parentheses show how these values are identified in a profile
data set:
– Compare type (CTYP)
– Listing type (LTYP)
– Browse setting (BRW)
– Process options (PROC1 and PROC2).
v Process statements copied from the statements data set that was specified in the
Statements Dsn field. This data set name is displayed and highlighted on the
SuperCE - Profile Manager panel. For example, the sample panel shown in
Figure 145 on page 231 displays the name SUPERC.STMTS.
If you leave the Statements Dsn field blank, the data set name and the words
preceding it are not displayed on the SuperCE - Profile Manager panel and
SuperCE does not include any process statements in your profile. See the
following sections for information about process options and process statements,
respectively:
– “Process Options - Select Process Options” on page 227
– “Edit Statements - Edit Statements Data Set” on page 228.
Note: New data set allocation block size parameters are controlled by the PDF
Configuration Table. See the ISPF Planning and Customizing manual for
details.
v Specify your own Statements data set initial edit macro name
v Enable or disable a new high performance program interface to SuperC. If you
select “Invoke SuperC via PROGRAM interface”, ISPF invokes SuperC directly.
Otherwise, ISPF invokes SuperC via a CLIST named ISRSFORG (ISRSSRCH for
Search-For). The CLIST interface may be useful if you need to customize the
allocations or wish to post-process the result. The PROGRAM interface is more
efficient and is the default.
SUPERC - Defaults
Command ===>
F1=Help F2=Split F3=Exit F9=Swap F12=Cancel
The Search-For utility (option 3.14) is a dialog that uses the SuperC program to
search your data sets or PDS members for one or more character strings. The
Search-For Utility panel, shown in Figure 147 on page 234, is the first panel of the
Search-For utility. The only requirements for this panel are:
v A string to be searched for, unless you select “Specify additional search strings”
v A data set to search, along with a volume serial and password if necessary.
A default listing data set name is provided if you choose not to enter your own.
ISPF Library:
Project . . .
Group . . . . . . . . . . . . .
Type . . . .
Member . . . (Blank or pattern for member selection list,
"*" for all members)
Other Partitioned, Sequential or VSAM Data Set:
Data Set Name . . .
Volume Serial . . . (If not cataloged)
Search String
A string to be searched for. No distinction is made between uppercase and
lowercase characters. Use the Extended Search-For utility (option 3.13.S) to
specify case-sensitive searches.
Four keywords—C, PREFIX, SUFFIX, and WORD—can help you narrow
the scope of a search. See “Search-For Strings and Keywords” on page 237
for information about these keywords and the rules that govern search
string entry.
Specify additional search strings
Select this field to have the Search-For utility search for more than one
string. The Search-For utility displays the panel shown in Figure 148 on
page 236, on which you can specify additional search strings. This panel
precedes a member list request.
If you do not select this option, the Search-For utility searches only for the
string entered in the Search String field.
Mixed Mode
Select this field to have the Search-For utility scan and parse the input data
set lines for DBCS text strings.
Note: The Word, Prefix, and Suffix Search-For qualifiers have no effect on
DBCS strings.
Bypass Selection List
When a member pattern is entered in the PDS Member List field or the
member name portion of the data set field (such as
MY.DATA.SET(pattern)), selecting this field causes SuperC to process all
members matching that pattern without displaying a member selection list.
Leaving this field blank causes the member list to be displayed.
Execution Mode
The processing mode you want to use when searching the data sets.
Specify one of the following:
1 Foreground. Searches the data sets and stores the results in the
data set specified in the Listing Data Set Name field. You can
browse the listing data set at the terminal.
2 Batch. Causes the display of the Search-For Utility - Submit Batch
Jobs panel so that you can specify job card and print disposition
information or edit the JCL statements. Then, Search-For submits
the batch job to search the data sets. See “Submitting a Search-For
Job in Batch Mode” on page 239 for more information.
where prefix is your TSO prefix and userid is your user ID. If your prefix
and user ID are identical, only your prefix is used. Also, if you do not
have a prefix, only your user ID is used.
If you enter a fully qualified data set name SuperC uses it as specified.
Otherwise, SuperC only appends your TSO prefix to the front of the data
set name specified. If you run with TSO PROFILE NOPREFIX, SuperC uses
the name as you entered it, which can result in an attempt to catalog the
name in the master catalog.
If you enter the name of a data set that does not exist, the Search-For
utility allocates it for you. The data set is allocated as a sequential data set
unless you enter a member name after it, in which case it is allocated as a
partitioned data set.
Entering the END command returns you to the Search-For Utility panel.
If you need to specify a DBCS string that contains a hexadecimal ’7D’ (x’7D’, the
hexadecimal representation of a single quotation mark) as half of a DBCS pair, you
must use the Enhanced SearchFor option (option 3.15) with the MIXED process
option.
Using Keywords
The following keywords can help you narrow the range of the search. If you do
not use a keyword, SuperC will find the string wherever it exists, even if that
happens to be in the middle of a word.
PREFIX Shows the string is preceded by a non-alphanumeric character,
such as a blank space. It cannot be used on the same line with
SUFFIX or WORD. For example, you can do this:
==> ELSE PREFIX
==> ELSE SUFFIX
Enter END command to process selections or CANCEL to leave the member list.
Note: Both the jump function (=) and the RETURN command cause an implied
cancellation of selections before they are carried out.
For more information about member lists, see the Using Member Selection Lists
section of the Libraries and Data Sets chapter of the ISPF User’s Guide Volume I.
//OUTDD DD . . . . .
// . . . . . . . . .
LRECL for the Listing Output will be 133
This panel allows you to specify one of the following Generate Output types:
v The SYSOUT class, which determines the printer to which your job is sent and
the format used for the printed output
v The name of a listing data set
v Output data definitions that you can use to give the printer additional
instructions, such as an output destination that is not defined by a SYSOUT
class.
The Job Statement information field is explained under the Job Statement
Information section of the Libraries and Data Sets chapter of the ISPF User’s Guide
Volume I. The other fields on this panel, as well as the options listed at the top of
the panel, are described in “Submitting a SuperC Job in Batch Mode” on page 217.
If you select option 3.15, the Extended Search-For Utility panel, shown in
Figure 151 on page 240, is displayed. This utility is a dialog that uses the SuperC
program to search your data sets or PDS members for one or more character
strings. It is appropriate if you need more flexibility than the standard Search-For
utility (option 3.14) provides.
You can also use SELECT process statements in the statements data
set to specify an optional set of PDS members to be searched.
However, the SELECT statement turns off the PDS member list
function.
CAPS A search string that you want the Extended Search-For utility to
find. This search string is converted to uppercase before the search
begins and is found only if it exists in the search data set in
uppercase.
The ANYC process option causes the string to be found in any
case, (uppercase, lowercase, or mixed case) even if you enter the
string in the CAPS field.
You can enter up to three uppercase search strings, one in each
CAPS field. Here are some examples:
example 1
Either of the following strings may be found in the search
data set:
CAPS . . . . THEN
CAPS . . . . IF
example 2
The following two strings must be found on the same line
because of the continuation (C) keyword. THEN must be a
complete word, while ISR must be the prefix of a word.
CAPS . . . . THEN WORD
CAPS . . . . ISR PREFIX C
example 3
In the next example, a hexadecimal string is specified as
the search string. Use this to find unprintable characters.
CAPS . . . . X’7B00’
example 4
The following example searches for the string JOE’S CLIST.
Notice that the string is enclosed in single quotation marks
and the apostrophe following Joe’s name has been
doubled.
CAPS . . . . ’JOE’S CLIST’
ASIS A search string that you want the Extended Search-For utility to
where prefix is your TSO prefix and userid is your user ID. If your prefix
and user ID are identical, only your prefix is used. Also, if you do not have
a prefix, only your user ID is used.
If you enter a fully qualified data set name SuperC uses it as specified.
Otherwise, SuperC only appends your TSO prefix to the front of the data
set name specified. If you run with TSO PROFILE NOPREFIX, SuperC uses
the name as you entered it, which can result in an attempt to catalog the
name in the master catalog.
If you enter the name of a data set that already exists, the contents of that
data set are replaced by the new listing output. However, if the data set is
sequential, you can add this listing to the data set instead of replacing it by
using the APNDLST process option.
If you enter the name of a data set that does not exist, Search-For allocates
it for you. The data set is allocated as a sequential data set unless you
enter a member name after it, in which case it is allocated as a partitioned
data set.
Process Options
Keywords that tell SuperC how to process the search-for operation. You
can type these keywords in the Process Options field or select them from a
panel. See “SuperC Compare Process Options” on page 397 for tables of
keywords.
Bypass Selection List
When a member pattern is entered in the PDS Member List field, selecting
this field causes SuperC to process all members matching that pattern
without displaying a member selection list. Leaving this field blank causes
the member list to be displayed.
Statements Dsn
The name of the data set that contains your search-for process statements,
which you can create or change by using option E on the Extended
"Search" Concatenation
DS1 . . .
DS2 . . .
DS3 . . .
DS4 . . .
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F12=Cancel
Figure 152. Extended Search-For - Concatenation Data Set Entry Panel (ISRSFCON)
For fields DS1 through DS4, use normal TSO naming conventions.
You can specify a series of concatenated data sets, an uncataloged
or password-protected data set, or a cataloged data set name.
Up to four data sets can be concatenated. Make sure the data sets
are concatenated in the proper sequence, as follows:
1. If two or more sequential data sets are concatenated as one
input data set, the data set attributes, such as block size, must
be identical.
2. PDS concatenations must have the data set with the largest
block size as the first in any concatenation.
3. Search-For uses only the first occurrence of a member in the
concatenated series of PDSs as source input for a search. Any
other occurrences of the member are ignored. You may specify
the SDUPM process option to cause SuperC to search for and
report all occurrences of the string for the entire concatenated
series of PDS members.
"Search" Concatenation
DS1 . . .
DS2 . . .
DS3 . . .
DS4 . . .
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F12=Cancel
This panel is the same as the panel shown in Figure 152 on page
243, except the Password field is omitted. If your data sets are
password-protected, search the data sets in foreground mode by
leaving the Option field on the Extended Search-For Utility panel
blank.
Search-For process options can affect how the input data is processed, and
determine the format and content of the output listing data set. They can also help
you save processing time by avoiding comments and blank lines.
All these options except the DPxxxx (do not process) options can be chosen from
the Search-For Process Options panel. However, you can type any of them in the
Process Options field on the Extended Search-For Utility panel. Errors caused by
mistyping process options are detected when you call the Extended Search-For
utility.
For definitions of the Search-For process options, see “SuperC Compare Process
Options” on page 397.
When you select 1 from the Options menu on the Extended Search-For Utility
panel, the Extended Search-For utility displays the statements data set you
specified in the Statements Dsn field. This data set is always displayed in Edit
mode, allowing you to add, change, or delete search-for process statements as
needed.
The size of the Edit window depends on the number of lines your terminal can
display. The sample panel shown in Figure 154 shows how the Edit window
appears on a 24-line display. Examples of some common process statements are
listed below the Edit window so you can easily compose the proper input line.
The SuperC program validates the process statements at run time. Invalid process
statements are not used and are noted at the bottom of the listing. Unless a higher
return code is required by some other condition, a return code of 4 is returned.
For the syntax and examples of the Search-For process statements, see “SuperC
Search-For Process Statements” on page 441.
When you run a foreground processor, you must wait until the processor ends
before doing anything else with ISPF. However, if you want to use ISPF while
waiting for the processor to end, submit the input as a batch job. You can do this
by using the Batch option if the processor you need is listed on the Batch Selection
panel, Figure 178 on page 285.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
The names of the foreground processors on this panel are point-and-shoot fields.
For more information, see the Point-and-Shoot Text Fields section of the ISPF User
Interface chapter of the ISPF User’s Guide Volume I.
1 General
2 Assembler
3 COBOL
4 VS Fortran
5 PL/I
6 VS Pascal
7 Binder/Link editor
8 SCRIPT VS
9 VS COBOL II debug
10 OS/VS COBOL debug
11 FORTRAN debug
12 Member parts list
13 C/370
14 REXX/370
15 Ada/370
16 AD/Cycle C/370
17 ISPDTLC
18 OS/390 C/C++
19 z/OS C/C++
Note: The Source Data Packed option has no effect on the Member parts list
option (4.12). Member parts list can read both packed and unpacked
data sets, so no expansion is needed.
4. When the Session Manager licensed program, 5740-XE2, is installed, you can
select the Session Manager mode option on the ISPF Settings panel so that
you enter Session Manager mode when you call any of the foreground
processors. Once you call Session Manager, it stays in effect for all logical
screens until you turn it off. For example, if you call Session Manager and
then split the screen, Session Manager will be in effect on both logical screens.
Note: If graphics interface mode is active, Session Manager does not get
control of the screen. Graphics interface mode is started when a
GRINIT service has been issued, but a GRTERM service has not been
issued. Refer to ISPF Services Guide for more information about these
two services.
5. Press Enter. ISPF displays the data entry panel for the processor you selected.
The remainder of this processing sequence applies to all foreground
processors except SCRIPT/VS, VS COBOL II interactive debug, COBOL
interactive debug, and Member Parts List. For these processors, use the
sequence referred to in the following list:
Processor Reference
SCRIPT/VS “SCRIPT/VS Processor (Option 4.9)” on page 265
VS COBOL II interactive “VS COBOL II Interactive Debug (Option 4.10)” on page
debug 272
COBOL interactive debug “OS/VS COBOL Debug (Option 4.10A)” on page 272
Member parts list “Member Parts List (Option 4.12)” on page 276
6. Enter the appropriate ISPF library and concatenation sequence or data set
name. If the input data set is partitioned, you can leave the member name
blank or use a pattern to display a member list. If you need help, see:
v the Naming ISPF Libraries and Data Sets section of the Libraries and Data
Sets chapter of the ISPF User’s Guide Volume I for help in entering library or
data set names
v the Displaying Member Lists section of the Libraries and Data Sets
chapter of the ISPF User’s Guide Volume I for information about patterns and
displaying member lists
v “Input Data Sets” on page 255 for information about the regular
concatenation sequence
v “Object Data Sets” on page 257 for information about object modules
v “Linkage Editor Concatenation Sequence” on page 265 for help with the
linkage editor concatenation sequence
VS FORTRAN has no LIB option, which some foreground processors use to
specify the input data set concatenation sequence. Therefore, the concatenation
sequence specified in the Group fields is used to find the member to be
compiled.
For FORTRAN interactive debug, the TYPE, or last qualifier, must be either
OBJ or LOAD. However, if you specify an OBJ data set as your input data set,
you must include a load library or data set in the input search sequence (see
step 11 on page 250).
7. This step applies to FORTRAN interactive debug only. Use the Source Type
field to tell ISPF the Type, or last qualifier, of the data set used to create the
input object module or load module.
8. Use the List ID field to tell ISPF what to name the output listing. See “List
Data Sets” on page 256 for more information.
9. Enter your password in the Password field if your input data set is
password-protected. See “Password Protection” on page 257 for more
information.
10. The Option field, whether ASSEMBLER, COMPILER, LINKAGE EDITOR, or
DEBUG, is remembered from one session to another. Therefore, you do not
need to change this field unless the options you need are not displayed.
Be careful not to enter any options that ISPF generates automatically. These
options are listed on the data entry panel. For more information about the
options available for your processor, refer to the documentation supplied with
that processor.
11. Enter any additional input libraries you need. For FORTRAN interactive
debug, enter any input LOAD libraries that you need to complete the search
sequence. These libraries must be LOAD libraries only. See “Input Data Sets”
on page 255 if you need help.
12. Once all the input fields have been specified, press Enter to call the
foreground processor.
If the Session Manager is installed and you selected Session Manager mode on
the ISPF Settings panel, the foreground processor and all function keys and
PA keys are under the control of the Session Manager. When foreground
processing is complete, you are prompted to enter a null line to return to ISPF
control.
If the Session Manager is not called, the PA and function keys have their usual
TSO-defined meanings; generally, the function keys are treated the same as
the Enter key.
13. Communication with foreground processors is in line-I/O mode. Whenever
you see three asterisks, press Enter.
14. If the foreground processor generated an output listing, the listing is
displayed automatically in Browse mode.
PK Print data set and keep K Keep data set (without printing)
PD Print data set and delete D Delete data set (without printing)
On this panel, the Data set name field shows the name of the list data set that
contains the output generated by the processor you selected. In the Option
field, enter one of the options shown at the top of the panel. The Print mode,
Batch SYSOUT class, Local Printer id or writer name, and Local SYSOUT
Class fields on this panel are described under “Hardcopy Utility (Option 3.6)”
on page 187. The Job statement information field is described under the Job
Statement Information section of the Libraries and Data Sets chapter of the
ISPF User’s Guide Volume I.
When you press Enter, the processor entry panel is displayed again. A
message indicating completion of the process is displayed in the upper-right
corner of the screen.
16. You can do one of the following:
v Enter other parameters and call the same processor.
v Enter the END command to return to the Foreground Selection panel and
select another processor.
v Enter the RETURN command to go to the ISPF Primary Option Menu.
v Use the jump function (=) to choose any primary option.
If the source data that you want to process is packed, it must be expanded before
it can be successfully processed by any of the language processors. The expansion
method you should use depends on whether your source data is:
v A sequential data set that contains expansion triggers
An expansion trigger is a keyword that tells ISPF to expand additional data before
copying, including, or imbedding it in the source data. Examples are INCLUDE
and COPY statements, and SCRIPT .IM (imbed) control words. For information
about defining your own expansion triggers, refer to ISPF Planning and
Customizing.
ISPF does not recognize expansion triggers in data stored as a sequential data
set. Therefore, for this type of data, you should follow these steps:
1. Manually expand the data that is to be copied, included, or imbedded in
your source data. To do this, edit the source data, enter the PACK OFF
command, and then save the data. When you have finished processing the
data, you can repack it by editing it again and entering PACK ON.
2. Select the Source Data Packed option before calling one of the language
processors.
v Either of the following:
– A sequential data set that does not contain expansion triggers
– Any member of a partitioned data set, either with or without expansion
triggers.
ISPF does recognize expansion triggers in data stored as members of a
partitioned data set. Also, if your source data does not contain expansion
triggers, you do not have to be concerned with them. Therefore, for these two
types of data, select the Source Data Packed option before calling one of the
language processors.
In each of the preceding situations, selecting the Source Data Packed option causes
ISPF to expand packed source data before it is processed. For partitioned data sets,
any included members are also expanded inline where the INCLUDE or COPY
statements, .IM SCRIPT control words, or other user-defined trigger statements are
found.
These scanners do not have all the sophistication of the actual language processors.
Therefore, unusual code or code that does not compile cannot be successfully
processed by member expansion. Examples are trigger statements:
v With comments that extend onto the next line
v That have compiler instructions to change the content of the code to be
included.
If an error occurs, the trigger statement is not expanded and is passed to the
language processor.
In SCRIPT/VS, if the error was found in a user trigger, one blank line is inserted
before and after the statement in question.
If an ISPF library is the input source, the member can be in any library in the
concatenation sequence. You can include additional input by using:
v The COPY statement for assembler and COBOL
v The INCLUDE statement for PL/I, FORTRAN, and Pascal
v The SCRIPT/VS imbed control word (.im)
v Macros
v Additional input libraries.
Whenever the input source is partitioned, you can specify additional input
libraries. They must be partitioned data sets that are not password protected. You
cannot specify additional input libraries if the input source is sequential. Specify
the fully qualified data set names, enclosed in apostrophes, such as:
Additional input libraries:
===> ’ABC.MACROS’
For example, in Figure 158 on page 259, a concatenation sequence of three ISPF
data sets and one additional input library has been specified. The concatenation
order is:
ISPFDEMO.XXX.ASM
ISPFDEMO.A.ASM
ISPFDEMO.MASTER.ASM
ISPFTEST.FLAG.ASM
The processor options are passed to the prompter exactly as you specify them.
For best results, if you plan to debug your program later using COBOL interactive
debug:
v Enter the name of the member being compiled in the List ID field if the input
data set is partitioned.
v If the input data set is sequential, enter the name of the sequential data set.
Then, when you debug your program, use these same names in the PROG ID
fields on the COBOL Interactive Debug panel.
where
prefix
is the data set prefix in your TSO profile, if you have one and if it is different from
your user ID,
userid
If you are using the same list data set for multiple job steps, be aware that the
DCB information can differ between the language processors and the linkage
editor, causing an I/O error when trying to read the list data set. We suggest that
you use a different list ID for each job step.
Password Protection
Input, object, interpretable text (ITEXT), and symbolic debug data sets can be
password-protected. You can specify the password in the Password field on the
foreground processor data entry panel. The password does not appear on the
screen when you enter it, but ISPF remembers it.
Since foreground processor panels have only one Password field, ISPF prompts
you if all data sets do not have the same password.
If you specify an ISPF library as the input source, ISPF writes object output from
the foreground assembler or compiler to a partitioned data set. This data set has
the same name as the first library in the concatenation sequence, but has a type of
OBJ. For example, if you specify PROJECT.LIB1.ASM as the first library name, the
object output is placed in data set PROJECT.LIB1.OBJ. The member name of the
object module is the same as the input member.
If you specify another data set, the object output is placed in a data set of the same
name, but with the last qualifier replaced by OBJ. If the data set name has only
one qualifier, OBJ is appended as the last qualifier. For example, if you specify an
input data set named OTHER.ASM or OTHER, the object output is placed in a
data set named OTHER.OBJ. For partitioned data sets, the object output is stored
in a member with the same name as the input member. For sequential data sets,
the object output is stored in a sequential data set.
Note: The object data set must exist before invoking a foreground or batch option
that creates an object module.
PK Print data set and keep K Keep data set (without printing)
PD Print data set and delete D Delete data set (without printing)
Printer Location . .
Printer Format . . .
Number of copies . .
Option ===>
F1=HELP F2= F3=END F4=DATASETS F5=FIND F6=CHANGE
F9=SWAP F10=LEFT F11=RIGHT F12=SUBMIT
Figure 157. Foreground Print Options Panel With TSO/E Information Center Facility
(ISRFPPRI)
List ID . . . Assembler
Password . . 1 1. High Level Assembler 2. Assembler H
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input Libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Assembler Options
Be careful not to enter the OBJECT and LIST options in this field. ISPF
generates these options automatically. OBJECT writes the output object
module to a partitioned data set. LIST writes the output listing to a list
data set. See “Object Data Sets” on page 257 and “List Data Sets” on page
256 for more information.
Assembler
Enables you to specify whether to use the High Level Assembler or
Assembler H. Specify a 1 for High Level Assembler or a 2 for Assembler
H.
List ID . . . . . . . Password . .
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Test If you plan to run interactive debug after you compile your program, enter
TEST in the Test field. Otherwise, enter NOTEST.
Other If you plan to run VS COBOL II interactive debug after you compile your
program, enter RESIDENT in the Other field. Otherwise, just enter any
other options you need.
Be careful not to enter the LIB and OBJECT options in the Other field. ISPF
generates these options automatically. LIB specifies the input data set
concatenation sequence. OBJECT writes the output object module to a
partitioned data set. See “Input Data Sets” on page 255 and “Object Data
Sets” on page 257 for more information.
List ID . . . . . . . Password . .
Compiler options:
Object . . (OBJECT or NOOBJECT)
Other . . .
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Object
ISPF does not automatically generate any options for VS FORTRAN.
Instead of generating an object module automatically, the VS FORTRAN
compiler allows you to decide whether to generate one. To generate an
object module, enter OBJECT in the Object field. To avoid generating an
object module, enter NOOBJECT. See “Object Data Sets” on page 257 for
more information.
Other If you plan to run FORTRAN interactive debug after you compile your
program, enter TEST in the Other field, along with any other options you
need.
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Compiler
Choose the compiler you want to use from the list presented.
Compiler Options
Enter any options you need in the Other field, except LIB, OBJECT, or
PRINT. ISPF generates these options automatically. LIB specifies the input
data set concatenation sequence. OBJECT writes the output object module
to a partitioned data set. PRINT writes the output listing to a list data set.
See “Input Data Sets” on page 255, “Object Data Sets” on page 257, and
“List Data Sets” on page 256 for more information.
List ID . . . . . . . Password . .
All the fields on this panel are explained in theLibraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Other Enter any options you need in the Other field, except LIB, OBJECT, or
PRINT. ISPF generates these options automatically. LIB specifies the input
data set concatenation sequence. OBJECT writes the output object module
to a partitioned data set. PRINT writes the output listing to a list data set.
See “Input Data Sets” on page 255, “Object Data Sets” on page 257, and
“List Data Sets” on page 256 for more information.
Processor
List ID . . . . . 1 1. Binder
Password . . . . 2. Linkage Editor
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Linkage editor/binder options
Enter any options you need, except LOAD, LIB, or PRINT. ISPF generates
these options automatically. LOAD writes the output object module to a
partitioned data set.
Note: Sequential data sets are invalid when using the Linkage Editor.
LIB specifies the input data set concatenation sequence. PRINT writes the
output listing to a list data set. See “List Data Sets” on page 256 and
“Object Data Sets” on page 257 for more information.
Binder
Determines whether the Linkage Editor (NOBINDER) or Binder (BINDER)
is invoked.
options. See “Input Data Sets” on page 255 and SYSLIN Data Set section
of the appendix called Allocation Data Sets in the ISPF User’s Guide
Volume I for more information.
where type is whatever you specify on the panel. For example, it can be OBJ or
some other type containing Linkage Editor language (LEL) control statements. If
the type is not OBJ, an OBJECT DDNAME is automatically allocated to ease the
use of the following Linkage Editor control statements:
INCLUDE OBJECT(member-name)
For example:
Project . . . XYZ
Group . . . . MYLIB . . . MASTER . . . . . .
Type . . . . LEL
Member . . . TOP
This concatenation sequence is used by the Linkage Editor to resolve automatic call
references.
Note: DCF requires the TSO profile prefix to be set. For additional information,
refer to DCF documentation.
When you select the SCRIPT/VS option, the first panel displayed is the
SCRIPT/VS Processor panel shown in Figure 164.
List ID . . . . . . . Password . .
Script Command . . . SCRIPT (SCRIPT or SCRIPTDB)
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, and Style, Display Style Options, and Browse Output option,
which are explained in the following sections.
The value you put in the Style field and whether or not you select the Display
Style Options and Browse Output options determine the following SCRIPT/VS
processing sequence:
1. For the Style field, you can do one of the following:
v Enter the name of an existing style.
You can enter the name of a style you have created or one of the styles
SCRIPT/VS creates for you: DRAFT and FINAL. These two styles
correspond to the formatting options available in the previous release of
SCRIPT/VS Foreground Processing. If you have not defined these options
before or if this is your first release of ISPF, the default values for the
SCRIPT/VS formatting options are set for you.
If you enter the name of an existing style in the Style field, that style is
used for formatting.
v Enter the name of a new style you want to define.
If you enter a new style name, the name is added to your style list. The
new style uses SCRIPT/VS formatting options that are equal to the
formatting options of the last style. Step 2 explains what to do to change
these options.
v Leave the Style field blank.
If you leave the Style field blank, ISPF displays the Select SCRIPT/VS
Formatting Style panel. This panel displays a list of the available styles. See
“Selecting a Formatting Style” on page 270 for more information.
2. Use a slash to select Display Style Options. ISPF displays the SCRIPT/VS
Options for Style panel, which shows the options that are currently being
used and allows you to change them. See “Changing Style Options” on page
270 for more information.
If you do not select Display Style Options, ISPF does not display the
SCRIPT/VS Options for Style panel.
3. Enter the appropriate ISPF library and concatenation sequence or data set
names. You can display a member list by omitting the member name or by
using a pattern. See the Libraries and Data Sets chapter of the ISPF User’s
Guide Volume I if you need help entering library or data set names, “Input
Data Sets” on page 255 for more information about the concatenation
sequence, and the Displaying Member Lists section of the Libraries and Data
Sets chapter of the ISPF User’s Guide Volume I for more information about
displaying member lists.
4. Enter your password in the Password field if your input data set is
password-protected. See “Password Protection” on page 257 for more
information.
5. Use the List ID field to tell ISPF what to name the output SCRIPT/VS listing.
See “List Data Sets” on page 256 for more information.
6. Use a slash to select the Browse Output option. ISPF displays your output in
Browse mode after it has formatted.
If you do not select the Browse Output option, ISPF skips Browse mode and
displays a Foreground Print Options for Style panel, shown in Figure 165 on
page 269.
7. Once all the input parameters have been specified, press Enter to call
SCRIPT/VS.
8. Communication with SCRIPT/VS is in line-I/O mode. Each time you see
three asterisks, press Enter. These asterisks, which usually appear at the
bottom of the screen, show that TSO is waiting for you to clear the screen
before it can proceed.
If the Session Manager is installed and you selected the Session Manager
mode option on the ISPF Settings panel, SCRIPT/VS and all PF and PA keys
are under control of the Session Manager. When formatting is complete, you
are prompted to enter a null line to return to ISPF control.
If the Session Manager is not called, the PA and function keys have their usual
TSO-defined meanings; generally, the function keys are treated the same as
Enter.
9. One or both of the following panels may appear, depending on your
treatment of the Style and Display Style Options fields. If both appear, they
will be in the following sequence:
a. Select SCRIPT/VS Formatting Style
b. SCRIPT/VS Options for Style
See “Selecting a Formatting Style” on page 270 and “Changing Style Options”
on page 270 if you need information about using these panels. When you are
finished with each panel, press Enter.
10. If SCRIPT/VS generated an output listing and you selected the Browse
Output option, the output is displayed automatically in Browse mode.
Otherwise, continue with the next step.
PK Print data set and keep K Keep data set (without printing)
PD Print data set and delete D Delete data set (without printing)
v Enter the END command to return to the Foreground Selection panel and
select another processor.
v Enter the RETURN command to go to the ISPF Primary Option Menu.
v Use the jump function (=) to choose any primary option.
Line
Cmd Style Description
The Select SCRIPT/VS Formatting Style panel is a list that can be scrolled and
contains all the styles available to you. Each style is a set of predefined formatting
options.
Type either S or D in the Line Cmd field and press Enter to select or delete a style,
respectively. You can only select one style at a time for formatting. However, one
or more styles can be deleted at the same time.
The display fields on the Select SCRIPT/VS Formatting Style panel contain the
following information:
Style The names of styles that you can either select or delete.
Description A reminder of the purpose of each style. Type over the description
to change it.
Figure 167 on page 271 shows the options available for the DRAFT style.
Bind: #Odd . .
#Even . .
Device type . . . . .
Chars (Fonts) . . . .
SYSVAR . . . . . . .
Page . . . . . . . .
The fields on the SCRIPT/VS Options for Style panel represent SCRIPT/VS
formatting options, all of which are optional. For a complete description of these
options, refer to Document Composition Facility: Generalized Markup Language Starter
Set User’s Guide.
If you enter the END command from the SCRIPT/VS Options for Style panel,
changes on this panel are not saved. If the style is new, it is saved with default
formatting options.
If you press Enter from the SCRIPT/VS Options for Style panel, SCRIPT/VS
processes the data set, and then one of the following occurs:
v A Browse panel is displayed if you selected the Browse Output option on the
SCRIPT/VS Processor panel. When you finish browsing the SCRIPT/VS
formatted output, a Foreground Print Options for Style panel is displayed.
Note: If you enter the PRINT parameter in the Other script parms field, the
Browse panel is not displayed.
v A Foreground Print Options for Style panel is displayed if you did not select the
Browse Output option on the Script/VS Processor panel.
See step 11 on page 268 for more information about printing SCRIPT/VS output.
PK Print data set and keep K Keep data set (without printing)
PD Print data set and delete D Delete data set (without printing)
Printer location . .
Printer Format . . .
Number of copies . .
Command ===>
F1=HELP F2= F3=END F4=DATASETS F5=FIND F6=CHANGE
F9=SWAP F10=LEFT F11=RIGHT F12=SUBMIT
Figure 168. Foreground Print Options for Style Panel with the TSO/E Information Center
Facility (ISRFP09I)
Prog ID . . . . . . . . . . . . . . . .
Print ID . . . . . . Password . .
Execution Parms:
===>
Additional input libraries:
===>
===>
===>
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except Prog ID, Print ID, Source, and Execution
Parms, which are explained in the following sections.
4. Enter your password in the Password field if your input data set is
password-protected. See “Password Protection” on page 257 for more
information.
5. The Source option tells ISPF whether to allocate the list data sets specified in
the Prog ID field. If you select Source, these data sets must already exist.
6. The Execution Parms field is remembered from one session to another.
Therefore, you do not need to change this field unless the parameters you need
are not displayed. Enter any parameters that you want ISPF to pass to the
program being debugged.
7. To continue COBOL interactive debug, return to step 12 on page 250.
Note: You do not need to allocate a symbolic debug data set for programs
compiled with VS COBOL II because the debug output, if requested, is
stored in the OBJECT module, which ISPF generates automatically.
When you allocate the data set, specify the same name as the data set that contains
your COBOL program, but:
v For an ISPF library, enter:
– The Group name you will specify in the first Group field on the Foreground
OS/VS COBOL Compile panel
– SYM in the Type field.
v For another partitioned or sequential data set, use SYM to replace the last
qualifier. For example, if COBOL.INPUT or COBOL is the input data set name,
allocate COBOL.SYM as the symbolic debug data set.
For partitioned data sets, including ISPF libraries, the debug output is stored in a
member with the same name as the input member. For sequential data sets, the
debug output is stored in a sequential data set.
When you run COBOL interactive debug, the names you put in the Prog ID field
on the COBOL Interactive Debug panel must be the same as the input member
names if you are to create a correct SYM data set.
You can avoid generating the print output by leaving the Print ID field blank,
even if you allocated the data set.
The last qualifier in the name of the data set you allocate must be TESTLIST. For
example, if you allocate a sequential data set named DEBUG1.TESTLIST and then
specify the Print ID as:
Print ID . . DEBUG1
where prefix is your TSO data set prefix, if you have one and if it is different from
your user ID, and userid is your TSO user ID. Use the following values to allocate
print output data sets:
Record format . . . . . FBA
Record length . . . . . 121
Block size . . . . . . 3146
The value you put in the Block Size field should be a multiple of 121, the record
length. Therefore, if your print output data is too large to fit within the
recommended block size (3146), increase this amount by using a multiple of 121,
such as 3267 or 3388.
Source Type . .
List ID . . . . . . . Password . .
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Debug Options
Enter any options you need, except LIB, SOURCE, or PRINT. ISPF
generates these options automatically. LIB specifies the input data set
concatenation sequence. SOURCE specifies the input source program,
whose type is identified in the Source Type field. PRINT writes the output
listing to a list data set. See “Input Data Sets” on page 255 and “List Data
Sets” on page 256 for more information.
The languages permitted in the member expansion function also are permitted in
the member parts list function, and the expansion triggers have the same
restrictions. See “Member Expansion (ISRLEMX)” on page 252. Besides the
expansion triggers, the member parts list also uses the CALL statements in
assembler, PL/I, COBOL, and VS FORTRAN. The format of the CALL statement
is:
CALL name
where the delimiter after the name can be either a left parenthesis, a blank, or a
valid statement delimiter. In COBOL, the CALL statement is valid only in the
PROCEDURE DIVISION, and the CALL PGMA and CALL ’PGMA’ statements both result in
a reference to the member name PGMA.
When you select the Foreground Member parts list option (4.12), the panel shown
in Figure 171 is displayed.
ISPF Library:
Project . . .
Group . . . . . . . . . . . . .
Type . . . .
Member . . . (Blank or pattern for member selection list)
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
The member parts list does not use the Source Data Packed option on the
Foreground Selection panel; both packed and unpacked data sets can be read.
Fill in the fields on the Foreground Member Parts List panel as follows:
1. Select one of the options listed at the top of the panel by typing its number in
the Option field.
2. Enter the appropriate ISPF library and concatenation sequence or data set
names. A blank member name results in a member list being displayed. You
can select only one member from this list. A pattern results in the processing of
all member names matching the pattern; an asterisk results in all members
being processed.
See the Libraries and Data Sets chapter of the ISPF User’s Guide Volume I if you
need help entering library or data set names, the Displaying Member Lists
section of the Libraries and Data Sets chapter of the ISPF User’s Guide Volume I
for information about using patterns and displaying member lists, and “Input
Data Sets” on page 255 for more information about the concatenation sequence.
3. The Language field is optional. It is used to specify the language in which the
source code is written. If you leave this field blank, ISPF uses the value in the
Type field as the default. However, the language must be one of the following:
v Assembler
v COBOL
v FORTRAN
v Pascal
v PLI
v SCRIPT.
4. In the Groups For Primary members field, enter a number from 1–4. This
number tells ISPF how many libraries in the concatenation sequence are to be
used in locating primary members. For example, if you enter 2, the first and
second libraries specified in the Group field are used to find primary members.
5. If you selected option 2 (write member parts data set), use the Data Set Name
field to tell ISPF where to write the output data set. The name you enter:
v Can be a sequential data set or a member of a partitioned data set
v Must follow standard TSO data set naming conventions.
If you enter the name of a data set that does not exist, ISPF allocates it for you.
6. Once all the input parameters have been specified, press Enter to call the
Foreground Member Parts List processor.
If the Session Manager is installed and if you specified Session Manager mode
on the Foreground Selection panel, the Foreground Member Parts List
processor and all function keys and PA keys are under control of the Session
Manager. When processing is complete, you are prompted to enter a null line
to return to ISPF control.
If the Session Manager is not called, the PA and function keys have their usual
TSO-defined meanings; generally, the function keys are treated the same as
Enter.
7. Communication with the Foreground Member Parts List processor is in
line-I/O mode. Each time you see three asterisks, press Enter. These asterisks,
which usually appear at the bottom of the screen, show that TSO is waiting for
you to clear the screen before it can proceed.
8. The option you chose in step 1 on page 277 determines what happens next.
The chain is broken when a member cannot be found in the set of concatenated
libraries or no more members are referenced. If a member cannot be found, the
name is flagged with an asterisk (*) and processing continues. For instance,
internally- called routines are not found.
When no more primary members can be found, the listing is printed, written, or
browsed. Calls to internal routines or variable names result in the member not
found flag being set.
The ISPDTLC interface panel appears as shown in Figure 173, Figure 174,
Figure 175, Figure 176, and Figure 177.
┌─────────────────────────────────────────────────────────────────────────────┐
│ Menu Utilities Commands Language Options Help │
│ ────────────────────────────────────────────────────────────────────────── │
│ ISPF Dialog Tag Language Conversion Utility - 5.5 │
│ │
│ Click here: Go to DTL input names 5-16 Reset DTL input names 2-16 │
│ Enter requested information: Current Language: ENGLISH │
│ More: + │
│ Member name . . . . . . . . (Blank or pattern for member list) │
│ DTL Source data set - 1 . . ’USERID.GML’ │
│ DTL Source data set - 2 . . │
│ DTL Source data set - 3 . . │
│ DTL Source data set - 4 . . │
│ Panel data set . . . . . . ’USERID.PANELS’ │
│ Message data set . . . . . ’USERID.MSGS’ │
│ Log data set . . . . . . . │
│ Log File Member name . . (Required when log file is a PDS) │
│ List data set . . . . . . . │
│ List File Member name . . (Required when list file is a PDS) │
│ SCRIPT data set . . . . . . │
│ Command ===> │
│ F1=Help F2=Split F3=Exit F7=Backward F8=Forward │
│ F9=Swap F10=Actions F12=Cancel │
└─────────────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────────────┐
│ Menu Utilities Commands Language Options Help │
│ ────────────────────────────────────────────────────────────────────────── │
│ ISPF Dialog Tag Language Conversion Utility - 5.5 │
│ │
│ Click here: Go to DTL input names 5-16 Reset DTL input names 2-16 │
│ Enter requested information: Current Language: ENGLISH │
│ More: - + │
│ SCRIPT data set . . . . . . │
│ Tables data set . . . . . . │
│ Keylist Application ID . . (Up to 4 characters) │
│ Enter "/" to select option │
│ / Replace Panel/Message/Script/Keylist/Command Members │
│ / Preprocess Panel Output │
│ Place ISPDTLC Messages in log file │
│ Suppress Messages (ISPDTLC formatting) │
│ Suppress Messages (CUA exceptions) │
│ / Use CUA Panel Attributes │
│ / Generate Statistics on Panel/Message/Script Members │
│ Generate List file │
│ Command ===> │
│ F1=Help F2=Split F3=Exit F7=Backward F8=Forward │
│ F9=Swap F10=Actions F12=Cancel │
└─────────────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────────────┐
│ Menu Utilities Commands Language Options Help │
│ ────────────────────────────────────────────────────────────────────────── │
│ ISPF Dialog Tag Language Conversion Utility - 5.5 │
│ │
│ Click here: Go to DTL input names 5-16 Reset DTL input names 2-16 │
│ Enter requested information: Current Language: ENGLISH │
│ More: - + │
│ Generate List file │
│ Generate List file with ENTITY substitution │
│ Generate Script file │
│ / Replace Log File Members │
│ / Replace List File Members │
│ List Source Convert Messages │
│ Use Expanded Log Message Format │
│ Allow DBCS │
│ Specify KANA │
│ Specify NOKANA │
│ / Create panels with Action bars │
│ / Create panels with GUI mode display controls │
│ Command ===> │
│ F1=Help F2=Split F3=Exit F7=Backward F8=Forward │
│ F9=Swap F10=Actions F12=Cancel │
└─────────────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────────────┐
│ Menu Utilities Commands Language Options Help │
│ ────────────────────────────────────────────────────────────────────────── │
│ ISPF Dialog Tag Language Conversion Utility - 5.5 │
│ │
│ Click here: Go to DTL input names 5-16 Reset DTL input names 2-16 │
│ Enter requested information: Current Language: ENGLISH │
│ More: - + │
│ / Create panels with GUI mode display controls │
│ / Add ISPDTLC version / timestamp to panels and messages │
│ Combine scrollable areas into panel )BODY section │
│ Display converted panels │
│ Display converted panels in a window │
│ Bypass data set name validation (after first cycle) │
│ / Enable graphic character display │
│ Use field names in place of Z variables │
│ Align DBCS prompt text with entry field │
│ Preserve leading ENTITY blanks when "space" is not specified │
│ Process multiple line comment blocks │
│ Scroll member list to last selected member │
│ Command ===> │
│ F1=Help F2=Split F3=Exit F7=Backward F8=Forward │
│ F9=Swap F10=Actions F12=Cancel │
└─────────────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────────────┐
│ Menu Utilities Commands Language Options Help │
│ ────────────────────────────────────────────────────────────────────────── │
│ ISPCP01 ISPF Dialog Tag Language Conversion Utility - 5.5 │
│ │
│ Click here: Go to DTL input names 5-16 Reset DTL input names 2-16 │
│ Enter requested information: Current Language: ENGLISH │
│ More: - │
│ Bypass data set name validation (after first cycle) │
│ / Enable graphic character display │
│ Use field names in place of Z variables │
│ Align DBCS prompt text with entry field │
│ Preserve leading ENTITY blanks when "space" is not specified │
│ Process multiple line comment blocks │
│ Scroll member list to last selected member │
│ Generate accessible character string │
│ Display additional DTL source data set list │
│ │
│ Conversion status message interval . . . 1 (0 - 999) │
│ DISPLAY(W) option check interval . . . . 1 (1 - 99) │
│ Command ===> │
│ F1=Help F2=Split F3=Exit F7=Backward F8=Forward │
│ F9=Swap F10=Actions F12=Cancel │
└─────────────────────────────────────────────────────────────────────────────┘
The fields on this panel are explained in ISPF Dialog Tag Language Guide and
Reference.
When you run a batch processor, you can continue using ISPF while the program
is running. However, if you run these processors by using the Foreground option,
you must wait for processing to end before doing anything else with ISPF. The
Foreground Selection panel is shown in Figure 155 on page 247.
===>
===>
===>
===>
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
The names of the batch processors on this panel are point-and-shoot fields. See the
Point-and-Shoot Text Fields section of the ISPF User Interface chapter of the ISPF
User’s Guide Volume I for more information.
For VS COBOL II interactive debug, enter the name of the input object
module or load module. The TYPE, or last qualifier, must be either OBJ or
LOAD. However, if you specify an OBJ data set as your input data set, you
must include a load library or data set in the input search sequence (see step
11).
ISPF displays a member list if you omit the member name or use a pattern.
See the Naming ISPF Libraries and Data Sets section of the Libraries and
Data Sets chapter of the ISPF User’s Guide Volume I if you need help entering
library or data set names, “Input Data Sets” on page 255 for more information
about the concatenation sequence, and the Displaying Member Lists section
of the Libraries and Data Sets chapter of the ISPF User’s Guide Volume I for
more information about displaying member lists.
Notes:
a. VS FORTRAN has no LIB option. However, the concatenation sequence is
still used to find the member to be compiled.
b. Password protection is not supported from the Batch option. Therefore, if
your input or output data sets are password-protected, use the Foreground
option, which does support passwords.
If you submit a job requiring a password- protected data set, the system
operator will be requested to enter the required password.
8. The List ID field tells ISPF what to name the output listing. Leave this field
blank and enter a SYSOUT class to send the listing to a printer. See “List Data
Sets” on page 256 for more information.
9. Enter a SYSOUT class to generate hardcopy of the listing. You can enter any
valid SYSOUT parameter. If a List ID is entered, this field is ignored.
10. The Options field, whether ASSEMBLER, COMPILER, or LINKAGE EDITOR,
is remembered from one session to another. Therefore, you do not need to
change these fields unless the options or parameters you need are not
displayed.
If you need information about the options available for your processor, refer
to the documentation that shipped with the processor.
11. Enter any additional input libraries you need. For VS COBOL II interactive
debug, enter any input LOAD libraries that you need to complete the search.
These libraries must be LOAD libraries only. See “Input Data Sets” on page
255 if you need help.
12. Once all the input fields have been specified, press Enter to call the batch
processor. ISPF generates the appropriate JCL statements. See “JCL
Generation—Compilers” on page 288 and “JCL Generation—Assemblers and
Linkage Editor” on page 290 for more information.
Note: You can leave the entry panel without generating any JCL by entering
the END command instead of pressing Enter.
13. One of the following occurs:
v If you used the jump function to bypass the Batch Selection panel, ISPF
submits the generated JCL and returns directly to the ISPF Primary Option
Menu.
ISPF calls the TSO SUBMIT command to submit a job. The SUBMIT
command displays the following message:
JOB useridA(JOB nnnnn) SUBMITTED
***
When you press Enter or any other interrupt key, ISPF returns to the
previous panel.
v Otherwise, ISPF returns to the Batch Selection panel with the message Job
step generated displayed in the short message area on line 1, as shown in
Figure 179.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
The job statement parameters are shown for information only. They are no
longer intensified, and you cannot type over them because the JOB
statement has already been generated. At this point, you can:
– Select the same or another processor to cause more JCL to be generated.
– Go to the ISPF Primary Option Menu by:
- Canceling the batch job by entering the CANCEL command
- Entering the END or RETURN command to cause the generated JCL to
be submitted for processing.
– Use the jump function (=) to choose any primary option. If any JCL has
been generated, it is submitted for batch processing.
JCL Generation—Compilers
Figure 183 on page 293 shows an example for the PL/I optimizing compiler. This
panel is typical of the batch compiler entry panels. After you fill in an entry panel
and press Enter, ISPF generates the appropriate JCL statements. The JCL that
would be generated for the PL/I example is:
//SCAN EXEC PGM=ISRLEMX,COND=(12,LE),
// PARM=(’PLI,TOPSEG,B,N,E,4, ,00,ENU,4,7’,
// ’1,/,VIO’)
//*
//* INSERT STEPLIB DD CARDS HERE FOR ISRLEMX AND THE NATIONAL
//* LANGUAGE LITERAL LOAD MODULE IF THEY ARE NOT IN YOUR SYSTEM
//* LIBRARY
//*
//ISRLCODE DD DSN=ISPFDEMO.XXX.PLIO,DISP=SHR
// DD DSN=ISPFDEMO.A.PLIO,DISP=SHR
// DD DSN=ISPFDEMO.MASTER.PLIO,DISP=SHR
//ISRLEXPD DD UNIT=SYSDA,DISP=(NEW,PASS),SPACE=(CYL,(2,2)),
// DSN=&&TEMP1
//ISRLMSG DD SYSOUT=(A)
//PLIO EXEC PGM=IEL0AA,REGION=1024K,COND=(12,LE),
// PARM=’MACRO,XREF’
//SYSPRINT DD DSN=ISPFDEMO.LISTPLIO.LIST,UNIT=SYSDA,
// SPACE=(CYL,(2,2)),DISP=(MOD,CATLG),
// DCB=(RECFM=VBA,LRECL=125,BLKSIZE=3129)
//SYSIN DD DSN=&&TEMP1,DISP=(OLD,DELETE)
//SYSLIB DD DSN=ISPFDEMO.XXX.PLIO,DISP=SHR
// DD DSN=ISPFDEMO.A.PLIO,DISP=SHR
// DD DSN=ISPFDEMO.MASTER.PLIO,DISP=SHR
// DD DSN=ISPFTEST.FLAG.PLIO,DISP=SHR
//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(2,2))
//SYSLIN DD DSN=ISPFDEMO.XXX.OBJ(TOPSEG),DISP=OLD
2. In this example, the second step calls the PL/I optimizing compiler by using
the temporary data set designated by &&TEMP1 as the input data set. The
concatenation sequence is passed to the compiler through SYSLIB DD
statements, to allow inclusion of subsidiary members referenced by
%INCLUDE statements in the source text.
The object module is directed to a partitioned data set with a three-level name
composed of the project name, the first library name, and a type qualifier of
OBJ. The member name for the object module is the same as the primary
member to be compiled.
The compiler listing is directed to SYSOUT class A, as specified.
where:
prefix The data set prefix in your TSO user profile
member For members of partitioned data sets, this is the same member
name specified on the entry panel. For sequential data sets, this
name is TEMPNAME.
Assembler
List ID . . . . . (Blank for hardcopy) 1 1. High Level Assembler
SYSOUT class . . . (For hardcopy) 2. Assembler H
Assembler options:
Term . . . (TERM or NOTERM)
Other . . .
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Term In the Term field, enter TERM if you want ISPF to generate a terminal data
set. A terminal data set contains a synopsis of the error messages produced
by Assembler XF. If the input data set is partitioned, the terminal data set
name is:
prefix.member.TERM
where prefix is the data set name prefix in your TSO user profile, if you
have one, and member is the name of the member being assembled.
However, if the input data set is sequential, the terminal data set name is:
prefix.TEMPNAME.TERM
Enter NOTERM in the Term field to avoid generating the terminal data set.
This is a required field.
Other Enter any other options you need in the Other field.
Compiler options:
Term . . . NOTERM (TERM or NOTERM)
Other . . .
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Term In the Term field, enter TERM if you want ISPF to generate a terminal data
set. A terminal data set contains a synopsis of the error messages produced
by Assembler XF. If the input data set is partitioned, the terminal data set
name is:
prefix.member.TERM
where prefix is the data set name prefix in your TSO user profile, if you
have one, and member is the name of the member being assembled.
However, if the input data set is sequential, the terminal data set name is:
prefix.TEMPNAME.TERM
Enter NOTERM in the Term field to avoid generating the terminal data set.
This is a required field.
Other If you plan to run VS COBOL II interactive debug after you compile your
program, enter TEST, RESIDENT, and any other options you need in the
Other field.
Compiler options:
Term . . . NOTERM (TERM or NOTERM)
Other . . .
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Term In the Term field, enter TERM if you want ISPF to generate a terminal data
set. A terminal data set contains a synopsis of the error messages produced
by the VS FORTRAN compiler. If the input data set is partitioned, the
terminal data set name is:
prefix.member.TERM
where prefix is the data set name prefix in your TSO user profile, if you
have one, and member is the name of the member being assembled.
However, if the input data set is sequential, the terminal data set name is:
prefix.TEMPNAME.TERM
Enter NOTERM in the Term field to avoid generating the terminal data set.
This is a required field.
Other If you plan to run FORTRAN interactive debug after you compile your
program, enter TEST in the Other field, along with any other options you
need.
Compiler options:
===>
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Compiler
Choose the compiler you want to use from the list presented.
Compiler options:
===>
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255.
Processor
List ID . . . . . (Blank for hardcopy) 1. Binder
SYSOUT class . . (For hardcopy) 2. Linkage Editor
Command ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, and the following:
Binder
Determines whether the Linkage Editor (NOBINDER) or Binder (BINDER)
is invoked.
where prefix is the data set name prefix in your TSO user profile, if you
have one, and member is the name of the member being assembled.
Note: Sequential data sets are invalid when using the Linkage Editor.
Leave the Term field blank to avoid generating the terminal data set.
Other Enter any other options you need in the Other field.
SYSLIB
The name of the data set that is to contain the ISPF library concatenation
sequence used to resolve any copy statements specified in your program.
See “Input Data Sets” on page 255 and the SYSLIB Data Set section of the
appendix called Allocation Data Sets in the ISPF User’s Guide Volume I for
more information.
SYSLIN
The name of the data set that is to contain the object module. The SYSLIN
field is provided to accommodate the VS Pascal XA and NOXA processing
Chapter 7. Batch (Option 5) 295
Batch—Binder/Linkage Editor (Option 5.7)
options. See “Input Data Sets” on page 255 and the SYSLIN Data Set
section of the appendix called Allocation Data Sets in the ISPF User’s
Guide Volume I for more information.
All the fields on this panel are explained in the Libraries and Data Sets chapter of
the ISPF User’s Guide Volume I, except List ID, which is explained in “List Data
Sets” on page 256, Additional input libraries, which is explained in “Input Data
Sets” on page 255, and the following:
Note: For VS COBOL II interactive debug, any additional input libraries that you
enter to complete the search sequence must be LOAD libraries only.
Debug command data set
In the Debug command data set field, enter the name of the data set that
contains the DEBUG command that you want VS COBOL II interactive
debug to enter during batch processing. Refer to VS COBOL II Application
Programming Debugging Guide for more information.
The only difference between this panel and the Foreground Member Parts List
panel is that option 1 (print member parts) is called Browse/Print member parts list
in foreground. The foreground version does not print your member parts list
unless you use the Foreground Print Options panel to do so.
Otherwise, this version operates the same as the foreground version. See “Member
Parts List (Option 4.12)” on page 276 for more information about using the
member parts list function.
The listing is 120 characters wide and uses ANSI printer controls.
ISPF Library:
Project . . .
Group . . . . . . . . . . . . .
Type . . . . SOURCE
Member . . . (Blank or pattern for member selection list)
The ISPDTLC interface panel is identical to that seen in the Foreground option.
This panel can be seen in Figure 173 on page 281, Figure 174, Figure 175,
Figure 176, and Figure 177.
Note: If you use this field, you will not have access to the new function
described in “The ISPF Command Shell Panel Saved Command Area” on
page 301.
v Session Manager mode, but only if this licensed program is installed. See “Using
the Session Manager” on page 302 for more information.
v A long command that continues on the following two lines.
===>
=>
=>
=>
=>
=>
=>
=>
=>
=>
=>
Note: The ISPF Command Shell panel action bar contains three pull-down choices
that let you control the saved command area.
v List
v Mode
v Functions.
Menu For more information, see the section on the Menu Action Bar Choice in
the ISPF User Interface chapter of the ISPF User’s Guide Volume I.
List The List pull-down offers you the following choices:
Note: The current setting will be shown as an unavailable choice; that is, it
will display in blue (the default) with an asterisk as the first digit of
the selection number (if you are running in GUI mode, the choice
will be grayed).
Update On Makes the list of commands in the saved command area
live; that is, new commands are appended to the list
automatically.
Update Off Makes the list of commands in the saved command area
static; that is, new commands are not appended to the list
automatically.
Mode The Mode pull-down offers you the following choices:
Note: The current setting will be shown as an unavailable choice; that is, it
will display in blue (the default) with an asterisk as the first digit of
the selection number (if you are running in GUI mode, the choice
will be grayed).
Retrieve Allows commands to be retrieved from the saved
command area and placed on the TSO Command Entry
field (==>) so that you can edit them before they are
executed. This mode is the default.
Execute Allows commands to be retrieved from the saved
command area and executed in one step.
Delete Allows you to delete commands from the saved command
area without executing the commands. Place the cursor on
the command to be deleted and press Enter. The command
will be blanked out. This process allows you to delete a
command if you are running with Update mode set off.
Functions
The Functions pull-down offers you the following choice:
Compress List Removes duplicate entries and blank spaces in the saved
command area if you are running with Update mode set
off. Entries are compressed automatically in Update mode.
TSO command
Sets the command shell to route commands to TSO
Workstation command
Sets the command shell to route commands to your
workstation.
Notes:
1. Workstation command is available only if you are
running the ISPF Client Server.
2. Any command may be prefixed with either TSO or WS to
override the command function setting.
Utilities
For more information, see the section on the Utilities Action Bar Choice in
the ISPF User Interface chapter of the ISPF User’s Guide Volume I.
Help The Help pull-down offers you the following choices:
1 General
2 TSO Command processor panel
3 Restrictions
4 Line I/O mode
5 Session Manager mode
6 Appendices
7 Index
===>
=> status
=> xmit carvm3.userid da(’userid.private.clist(types)’)seq
=> TIME
=> RECEIVE
=> XMIT CARVM3.SCOTT DA(’USERID.PROJ.PANELS(ISAJP10)’) SEQ
=> PERMIT ’BOB.*’ GENERIC ACCESS(READ) ID(*)
=> rexec -1 SQUIRT -p SPARKY p:\acI13\samples\isr prim\os213\isr_prim
=> XMIT CARVM3.userid DA(’USERID.BUILD.LIST77’)
=> ssdf
=> XMIT CARVM3.userid DA(’USERID.trace’)
Figure 189. ISPF Command Shell Panel with Saved Commands (ISRTSO)
TSO commands, CLISTs, and REXX EXECs entered are invoked using the ISPF
SELECT CMD service. Variable names starting with an ampersand (&) are
evaluated by ISPF. If you want the underlying command processor to see the
ampersand you must specify 2 ampersands. For example:
For example, the HELP, PRINT, and CANCEL commands are interpreted as the
ISPF HELP, PRINT, and CANCEL commands, unless you precede them with TSO.
Therefore, to get TSO HELP information, enter:
===> TSO HELP xxx
Note: Remember that a command issued through an alias may contain some of the
characteristics listed here and thus may cause unwanted results.
Note: Refer to ISPF Planning and Customizing for information on altering the PDF
configuration table to allow you to enter Session Manager mode.
If you select this option, any display output is displayed in the Session Manager
TSOOUT stream.
Note: If GDDM/ISPF mode is active, Session Manager does not get control of the
screen. GDDM/ISPF mode is started when a GRINIT service has been
issued, but a GRTERM service has not been issued. Refer to ISPF Services
Guide for more information about these two services.
The function key definitions are not transferred to the Session Manager from ISPF.
When the command ends, the Session Manager prompts you to enter a null line to
return to ISPF control and displays the TSO Command Processor panel again when
you do so.
If you do not select Session Manager mode, terminal I/O occurs as though the
Session Manager were not installed. The terminal operates in normal TSO fashion.
Any communication with the command is in line-I/O mode. When the command
302 z/OS V1R6.0 ISPF User’s Guide Vol II
Command (Option 6)
ends, three asterisks (***) are displayed. Press Enter to display the TSO Command
Processor panel again in full screen mode.
To interrupt a TSO command, CLIST, or REXX EXEC, press the PA1 key. The TSO
command ends and the TSO Command Processor panel is displayed again. If
terminal input is inhibited, press the Reset key before pressing the PA1 key. If you
are in Session Manager mode, enter a null line to return to ISPF full screen mode.
When the TSO Command Processor panel is displayed again, the command that
was just processed is displayed to the right of the arrow. Enter another command
or the END command to return to the ISPF Primary Option Menu.
For terminals with primary and alternate screen sizes, ISPF does not check to make
sure the same screen settings are in effect when a command, CLIST, or REXX
EXEC ends. If you call a CLIST, REXX EXEC, or command that changes the screen
settings, you are responsible for saving and restoring them before control is
returned to ISPF.
Dialog Test (option 7) provides you with facilities for testing both complete ISPF
applications and ISPF dialog parts, including functions, panels, variables,
messages, tables, and skeletons. The Dialog Test option allows you to:
v Call selection panels, command procedures, and programs
v Display panels
v Add new variables and change variable values
v Display a table’s structure and status
v Display, add, modify, and delete table rows
v Browse the ISPF log
v Process dialog services
v Add, modify, and delete function and variable trace definitions
v Add, modify, and delete breakpoint definitions.
You can use TSO TEST to complement this option if you want to examine and
manipulate non-ISPF storage areas.
Any requested traces for variable usage and dialog service calls are written to the
ISPF log. You can browse the log using the Log option (7.5).
If you define a breakpoint and the function gets to it, dialog processing is
suspended, and Dialog Test displays the Breakpoint Primary Option Panel
(Figure 212 on page 350). At this point, you can access and manipulate dialog
parts, such as variables, tables, and so forth. Then, if you select the Go option from
the Breakpoint Primary Option Panel, the dialog resumes processing.
When the processing is complete, you are returned to the Functions option (7.1). If
you select the Cancel option from the Breakpoint Primary Option Panel, the dialog
is cancelled and the first primary option panel that you were shown during your
terminal session is displayed again. For example, if the first screen displayed when
you began your session was a master application panel that is different from the
ISPF Primary Option Menu, that master application panel is displayed again.
When you enter Dialog Test from the ISPF Primary Option Menu, you enter a new
user application with an ID of ISR. When you enter Dialog Test from the ISPF
primary option panel, you enter a new user application with an ID of ISP. All
options listed on the Dialog Test Primary Option Panel operate in this context. If
you call a new function using the Functions options (7.1), a SELECT service call is
performed, and the rules for the SELECT service are followed.
Option ===> 7
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Note: You can set the application ID under which you enter the Dialog Test
function using the Dialog Test appl ID... choice from the Options pull-down
on the ISPF Primary Option Menu or using the Dialog Test appl ID... choice
from the Test pull-down on an Edit panel.
After you begin an application under Dialog Test, you can enter the DTEST
command with one of its parameters as a quicker way to start a dialog test
function. For example, if you enter DTEST 8 on the command line, the Option 7.8
Breakpoints panel appears. The other parameters of the DTEST command also
match the dialog test function they perform:
1 invoke Functions panel
2 invoke Display Panel panel
3 invoke Variables panel
4 invoke Tables panel
5 display browse log panel
6 invoke Dialog Services panel
7 invoke Traces selection panel
8 invoke Breakpoint panel
You must use a parameter with the DTEST command, otherwise an error message
appears. After you complete the entries on whichever dialog test panel you invoke,
leaving the panel returns you to the application you were running with the new
entries in place.
Dialog Test is itself a dialog and, therefore, uses dialog variables. Since it is
important to allow your dialog to operate without interference, as though in a
production environment, Dialog Test accesses and updates variables independently
of your dialog variables.
All breakpoints and traces that you set in Dialog Test exist only while you remain
within the Dialog Test option.
You should always allocate the ISPF log when using Dialog Test. Do not suppress
its generation by typing 0 in the Primary pages field that appears on the Log Data
set defaults... and List Data set defaults... choices from the Log/List pull-down on
the ISPF Settings panel. Dialog Test writes trace data to the log when you request
it. Also, if Dialog Test finds an unexpected condition, it writes problem data to the
log.
When you enter Dialog Test, you are given the following ISPF facilities:
v All functions you normally get by specifying the TEST parameter on the
ISPSTART command
v The logging of all severe errors, both from user dialogs and Dialog Test. This is
normally done when you specify TRACE or TRACEX on the ISPSTART
command.
v The suspension of the logging of all ISPEXEC dialog service requests. Such
logging normally occurs when you specify TRACE or TRACEX on the ISPSTART
command. You should use the Traces option (7.7).
These facilities become active for all logical screens when you are using split-screen
mode. At the completion of the last dialog test session (dialog test is no longer
active in any logical screen), these options will be restored to the original values
established during dialog manager start-up. Optionally, by making the appropriate
selection on the ISPF Settings panel, the facilities established by dialog test will
remain in effect after the last dialog test session terminates.
Using Variables
When you select the Dialog Test option from the ISPF Primary Option Menu, you
are given a new function pool, a new shared pool, and the profile pool for the
application ID under which you entered Dialog Test. When you select Dialog Test
from the ISPF Primary Option Menu, you are given a new function pool, a new
shared pool, and the ISPPROF profile pool. These pools are used if you set a
variable, display a panel, call an ISPF service, and so forth. When you call a new
dialog, Dialog Test uses the SELECT service, and follows the rules for the creation
of new variable pools. For example, if you call a new dialog using the NEWPOOL
option, Dialog Test creates new shared and function variable pools for you. The
profile variable pool, ISRPROF or ISPPROF, remains as it was.
If you set a dialog variable in the shared pool from a dialog running under Dialog
Test and then call the dialog again from the Command line, you cannot retrieve the
value of that variable.
Dialog variables should be initialized and set in the context of the dialog’s
processing. A dialog’s function variable pools are created when it is called; that is,
when the SELECT is done. Therefore, to set function variables in newly created
pools, you must define a breakpoint early in your dialog’s processing, at a point
before the function is called.
For example, if you call a dialog with the NEWPOOL parameter, you must define
a breakpoint in the dialog before the first function is called to access that dialog’s
function and shared variable pools. You can change the dialog’s profile variable
pool before calling the dialog, since a new profile variable pool is not created.
When your dialog ends, all variable pools that were created when the dialog was
called are deleted.
Note: ISPF does not support TSO global variables. You can find a severe dialog
test error when testing a dialog that refers to a global variable.
Note: If you choose not to continue dialog testing, you return to the ISPF Primary
Option Menu. The TEST and TRACE options set by dialog test are restored
to the values originally established during dialog manager start-up.
Optionally, by making the appropriate selection on the ISPF Settings panel,
the facilities established by dialog test will remain in effect after the last
dialog test session terminates.
If you find a severe error when manipulating your dialog at a breakpoint, Dialog
Test assumes that the CONTROL service ERRORS setting is CANCEL. For
example, if you display a panel at a breakpoint and that panel is not found, the
Error Message panel is displayed. This occurs even if your current dialog has an
ERRORS setting of RETURN.
Regardless of the ERRORS setting, all your severe errors are logged.
If Dialog Test finds a severe error during its processing, the details are logged and
the following message is shown to you on an error message display:
Test severe error
Details precede this message in the ISPF log
You should browse the ISPF log to find the problem; see “Log (Option 7.5)” on
page 336 for more information.
Commands
You can enter ISPF primary commands on Dialog Test panels. Seven commands
have special meaning during Dialog Test operations. You enter them in the
Command line of the applicable Dialog Test option panel. These commands, and
the Dialog Test options with which they function, are:
Primary Command Valid Options
CANCEL
v Variables (option 7.3)
v Tables (option 7.4)1
v Traces (option 7.7)2
v Breakpoints (option 7.8)
END
v Variables (option 7.3)
v Tables (option 7.4)3
v Traces (option 7.7) 2
v Breakpoints (option 7.8)
LOCATE
v Variables (option 7.3)
v Tables (option 7.4)4
v Traces (option 7.7) 2
v Breakpoints (option 7.8)
NEXT/PREV
v Tables (option 7.4)4
QUAL
v Breakpoints (option 7.8)
RESUME
v Breakpoints (option 7.8)
SORT
v Variable (option 7.3)
Dialog Test has three line commands that have special meaning during testing
operations. These commands, and the options with which they function, are:
Line Command Valid Options
D (delete)
v Variables (option 7.3)
v Tables (option 7.4) 1
v Traces (option 7.7) 2
v Breakpoints (option 7.8)
I (insert)
v Variables (option 7.3)
v Tables (option 7.4) 1
v Traces (option 7.7) 2
v Breakpoints (option 7.8)
R (repeat)
v Tables (option 7.4) 1
v Traces (option 7.7) 2
v Breakpoints (option 7.8)
When using the Dialog Test primary and line commands, you should be aware of
the following:
v You can specify both a primary command and line commands before you press
the Enter key.
v You can enter multiple line commands on the display.
v You cannot carry out a deletion if one of the included lines contains another line
command.
v You can delete lines that contain an input error.
v The line commands are processed in row order when you press the Enter key.
Any fields changed in the row are handled before a line command is processed.
Saving Changes
The END command ends the current option. Any changes made to the data now
take effect.
LOCATE string
where:
string
The character string you are trying to find. If the string ends in an asterisk (*),
a scan for the characters preceding the asterisk is done. The asterisk is optional
in the Variables option (option 7.3).
The same breakpoint qualification data can be obtained using the Qualifications...
choice on the Qualify pull-down.
D – Deleting Lines
The D command deletes one line or n lines starting with this line. The syntax is:
D[n]
If you are using the Variables option (7.3), the n operand does not apply. To avoid
conflict with the I (insert) line command, the Variables option does not allow you
to type a number along with the D command to delete more than one line
simultaneously. Therefore, enter a single D line command on each line you want to
delete. You can enter this command on more than one line before pressing the
Enter key.
I – Inserting Lines
The I command inserts one line or n lines directly after this line, with underscores
and quotation marks in the appropriate fields. The syntax is:
I[n]
R – Repeating Lines
The R command repeats this line once or n times. The syntax is:
R[n]
On the Keylist Change panel, you can reassign existing function keys by typing
over the information in the data fields, or create a new function key assignment to
suit your needs. For example, you could assign the GO command to F4 if you
typically issue GO many times during a dialog test.
If you press F3 or select Save and Exit from the File pull-down, the values that you
have assigned will be valid when you return to Dialog Test. If you select Cancel
from the File pull-down, the fields return to their original values.
If you call a new function or selection panel at a breakpoint, the previous function
or selection panel is suspended and the new one is processed. When the new
activity finishes, the Invoke Dialog Function/Selection Panel is displayed. The old
activity resumes when you enter the END command. When the originally-called
function finishes processing, the Invoke Dialog Function/Selection Panel is
displayed again.
When you select the Functions option, the scrollable panel shown in Figure 192 is
displayed to allow you to specify the dialog function that you want to test. Press
F8=Forward to display the rest of the panel.
There are two alternate Invoke Dialog Function/Selection panels, ISPYFPA and
ISPYFPB. ISPYFPA is formatted with the most often used fields at the top of the
scrollable area. ISPYFPB is similar, but it has a selection field for panel, command,
program, or request selection. Unlike panel ISPYFP and ISPYFPA, when you use
ISPYFPB the panel, command, program, and request selection fields can all contain
values.
You can specify one of the alternate panels using ISPF’s Configuration utility. Refer
to the ISPF Planning and Customizing manual for more information.
One of the advantages of placing dialog panels in pop-up windows is that you can
move the pop-up within the 3270 physical display area to reveal portions of the
underlying panel.
See ISPF Dialog Developer’s Guide and Reference for instructions on how to move a
pop-up window.
If you leave this field blank, the % prefix has its normal effect. The
valid values for this field are:
LINE Used to enter line mode when calling a CLIST or REXX
EXEC.
FSCR Used to enter full-screen mode when calling a TSO
command.
Invoke program:
Use the following fields to call a program:
PGM The name of a program to be called as a dialog function.
PARM Optional parameters to be passed to the program. This input field
continues onto the next line on the panel.
MODE
An optional parameter used to tell ISPF whether to display the
program results in line mode or full-screen mode. If you leave this
field blank, ISPF uses line mode as the default. The valid values
for this field are:
When you select the Panels option (7.2), the panel in Figure 193 on page 317 is
displayed.
Option ===> 7
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Cursor position
An integer specifying the position in the field where the cursor is to be
placed.
Message pop-up field
The name of a panel field the pop-up message window should be placed
adjacent to. Note that the message definition determines if the message
will appear in a pop-up window.
Display in window
A slash ( /) specifies that the panel is to be displayed in a pop-up window.
If you specify a panel name, entries in Message id, Cursor field, Cursor Position,
Message pop-up field, and the Display in window option are optional.
With the exception of the Display in window option, these are the same
parameters that a dialog function can specify when calling the DISPLAY service.
Selecting the Display in window field is the functional equivalent to the dialog
issuing an ADDPOP service before the DISPLAY service.
When the panel is displayed, the )INIT and )PROC sections of the panel are
processed in the same way the DISPLAY service would process them.
If you want to set variables before you display the panel, you can use the Variables
option (7.3) to do so. When you display the panel, you can type in new data or
type over existing data, and then verify the variables by using the Variables option
(7.3) again. Data that you type on the panel is retained until you change it, leave
Dialog Test, or reset the function pool.
Figure 194 on page 319 shows the panel that is displayed if you specify
message ID ISPD241 and, optionally, a cursor position without identifying a panel
name. The long message portion of the identified message is displayed when you
enter the HELP command on that panel.
Invalid option
┌────────────────────────────────────────────┐
│ The option that was entered was not valid. │
└────────────────────────────────────────────┘
Command ===>
F1=HELP F2= F3=END F4=DATASETS F5=FIND F6=CHANGE
F9=SWAP F10=LEFT F11=RIGHT F12=SUBMIT
When you enter the END command from the panel being tested, the Display Panel
reappears on the screen.
When you select this option, you can scroll a display showing all the current
variables for the dialog being tested, as shown in Figure 195 on page 320.
In addition to scrolling capability, you can also increase the size of the Variables
pop-up window to fill the entire 3270 physical display area using the RESIZE
command. The initial RESIZE command increases the pop-up window to its
maximum size, and the following RESIZE reduces the window to its original size.
The Variables display is controlled by the selection you make in the View
pull-down on the Dialog Test Primary Option Panel action bar:
1 Display Variables in window. Variables are displayed in a pop-up
window.
2 Display Variables full-screen. Variables are displayed full-screen.
Note: The current setting will be shown as an unavailable choice; that is, it
will display in blue (the default) with an asterisk as the first digit of
the selection number (if you are running in GUI mode, the choice
will be grayed).
Variables Commands
The Variables option (7.3) uses the CANCEL, END, and LOCATE commands, and
the I (insert) and D (delete) Dialog Test line commands described in “Commands”
on page 309. You can change the displayed sort order using the SORT command.
SORT with no operands sorts the list by variable pools then by variable name.
SORT NAME sorts the list by variable name and then by variable pool. SORT
VALUE sorts the list by the displayed Value field. The LOCATE command can be
used to search for a specific variable. LOCATE accepts as an operand the name, or
first letters of the name of a variable. If the name is not found, the list is positioned
near the closest match. You can use the RFIND key to continue searching other
variable pools.
Normally, the variable pools are updated with the data from the display when you
use the END command to leave the option.
Manipulating Variables
The rows of the display are sorted in the following order:
1. By pool (function, then shared, then profile)
2. By function pool type (V, then I)
3. Alphabetically by variable name within each pool.
Insertions are left where they are typed on the display. Changes to the display are
processed when you press the Enter key. Updating of the variable pools occurs
when you enter the END command.
New function pool variables are given an I (implicit) attribute and a CHAR format.
If you type F in the attribute field, ISPF changes it to I.
By using the second method, you can interchange the values of two or more
variables by simply changing their names. For example, you can interchange the
values for variables A and B by changing the variable name A to B and name B to
A, and then pressing the Enter key.
Deleting Variables
Any dialog variable in the shared and profile pools can be deleted, unless it has an
N attribute. Though you cannot delete a variable from the function pool, you can
set its value to blanks.
To delete a variable, use the D line command. However, to avoid conflict with the I
(insert) line command, the Variables option does not allow you to type a number
along with the D command to delete more than one line simultaneously. Therefore,
enter a single D line command on each line you want to delete. You can type this
command on more than one line before pressing the Enter key.
where:
n An integer 0 through 9 or an alphabetic character A through F.
There must be an even number of characters within the quotation
marks.
DBCS data
A variable defined as DBCS by the VDEFINE service or displayed through
the field with FORMAT(DBCS) specified in the test environment is
displayed using the form:
’¬[DBDBDB]’
where:
[ and ] Represent the SO (shift-out) and SI (shift-in) characters,
respectively.
If you type a DBCS value in this format on the Variables panel, only the
DBCS characters are stored.
9 Display Status
10 Usage Notes
11 View Action Bar
12 General Dialog Test
where:
[ and ] Represent the SO (shift-out) and SI (shift-in) characters,
respectively. For an abbreviated search, type a 2-byte
asterisk (*) at the end of the DBCS value. For example:
¬[DBDB**]
where:
If you type a DBCS value in this format on the Modify Row panel
or the Add Row panel, only the DBCS characters are stored,
regardless of the DBCS column specification.
Option The number of one of the functions displayed on the Tables panel.
Once you specify a table name, it is retained until you change it or until you leave
Dialog Test.
For the Display row (1), Delete row (2), Modify row (3), and Add row (4) options
of the Tables option (7.4), you must identify the row you want to display, delete,
modify, or add. To do this, you can specify a row number in the By row number
field, or you can use the Variable and Value fields to specify a list of search
operands. To show the current row, leave the asterisk in the By row number field.
If you specify both a row number and a search operand, the row number is used
and the search operand is ignored.
The current row pointer in the table can be changed only at your request or by
your dialog.
The list of search operands consists of variable names and values that allow you to
specify the values that specific variables have in a row. You can specify the
complete value, abbreviate the value with an asterisk to find a row containing a
variable beginning with specified characters, or leave the row blank. The search
begins with the row following the current row. If a row matching the search
operand is not found, the current row pointer is set to the top. You can repeat the
search, if necessary.
1—Display row
You can use the Display row option to display the contents of an existing row in
an open table. When you select the Display row option, do the following on the
Tables panel:
v Specify the name of a table in the Table Name field. If the table is not open,
specify NOWRITE or WRITE in the Open tables field.
v Specify a row number or a search operand list to identify a row.
Note: Use the View action bar choice on the Tables panel to specify whether this
display is to be in a pop-up or full-screen.
When you press Enter, you are shown the table row data on a display that you can
scroll (Figure 197). The pop-up window can also be resized using the RESIZE
command. In the figure, the variables constitute one table row.
Display Row Commands: The Display Row option uses the END and LOCATE
commands described in “Commands” on page 309.
2—Delete row
You can use the Delete row option to remove an existing row from an open table.
When you select the Delete row option, do the following on the Tables panel:
v Specify the name of a table in the Table Name field. If the table is not open,
specify NOWRITE or WRITE in the Open tables field.
v Specify a row number or a search operand list to identify a row.
When you press Enter, a panel is displayed (Figure 198 on page 328) to allow you
to confirm the delete request.
Press Enter to delete the row, or enter the END or CANCEL command to cancel
the deletion.
3—Modify row
You can use the Modify row option to change the contents of an existing row of an
open table. When you select the Modify row option, do the following on the Tables
panel:
v Specify the name of a table in the Table Name field. If the table is not open,
specify NOWRITE or WRITE in the Open tables field.
v Specify a row number or a search operand list to identify a row.
Note: Use the View action bar choice on the Tables panel to specify whether this
display is to be in a pop-up or full-screen.
When you press Enter, a display that you can scroll (Figure 199 on page 329) is
shown. The pop-up window can also be resized using the RESIZE command.
Each line on the panel represents a variable in row 6 of the table and contains a
line command field and the following fields:
Variable Variable name, modifiable only for save variables.
T Type of variable, non-modifiable:
K Key variable.
N Name variable; non-key.
S Save (extension) variable.
A Attribute of each variable, non-modifiable:
T Truncated to 2048 characters for display.
Value Value of the variable, up to 2048 characters.
Type in new values or change the current values for the key, name, and save
variables in the Value column. Enter new save variables by typing over the
underscores in the Name column with the variable names and specifying the
desired values. The underscores are pad characters; you do not need to blank them
out.
v If you delete a save variable, assume that the variable no longer exists in this
row.
v If more than one variable entry has the same name, all instances of that variable
are assigned the value of the last occurrence of the variable; that is, the
occurrence closest to the bottom of a display that you can scroll.
v Blank save names are ignored and do not need to be deleted, even if data is left
in the value.
v Hexadecimal data that usually cannot be displayed is converted to characters
that can be displayed or is typed by using the form:
X’nnnnnnnn’
where:
n An integer 0–9 or an alphabetic character A–F. There must be an even
number of characters within the quotation marks.
v Variables defined with the VDEFINE service as non-character are shown in
converted form; do not change them by using the hexadecimal representation. A
format or length error causes a message to be displayed when you use the END
command.
v When you leave the Modify row option by using the END command, the row is
replaced, and the message Row modified is issued.
Modify Row Commands: The Modify row option uses the CANCEL, END, and
LOCATE commands, and the D (delete), I (insert), and R (repeat) Dialog Test line
commands described in “Commands” on page 309. Inserted and repeated lines
always have a type of S, because you can add only save variables to a row of an
existing table. also, you can delete only save variables.
4—Add row
You can use the Add row option to add a new row after a selected row of an
opened table. When you select the Add row option, do the following on the Tables
panel:
v Specify the name of a table in the Table Name field. If the table is not open,
specify NOWRITE or WRITE in the Open tables field.
v Specify a row number or a search operand list to identify a row.
Note: Use the View action bar choice on the Tables panel to specify whether this
display is to be in a pop-up or full-screen.
When you press Enter, a display that you can scroll is shown (Figure 200),
containing all the key and name variables in the table. The pop-up window can
also be resized using the RESIZE command.
Each row of the display contains a line command field and the following fields:
Variable Variable name.
T Type of variable, non-modifiable:
K Key variable.
N Name variable; non-key.
S Save (extension) variable.
A Attribute of each variable. This attribute is non-modifiable and is
not used for this option.
Value Space for the variable value to be added, up to 2048 characters.
Type the values for the key and name variables in the Value column, which is
originally initialized to all nulls. You cannot change the names of the key and
name variables because they were established when the table was created.
You can enter save variables, identified as TYPE S, by typing over the underscores
with the save variable names and specifying the desired values. The underscores
are pad characters; you do not need to blank them out.
You can add a row with no values to the table, but you are asked to confirm such
an action to guard against inadvertent use of the END command.
When using the Add row option, be aware of the following points:
v The position of the new row in the table depends on whether the table was
previously sorted using the TBSORT dialog service. If the table was sorted, the
new row is placed in sort order; if it has not been sorted, the new row is placed
after the row you specified.
v You cannot delete a key or name variable and its value from the display or table
row.
v You cannot change the variable name for a key or name variable; if you do, an
error message is displayed and the original name is restored.
v If more than one variable entry has the same name, all instances of that variable
are assigned the value of the last occurrence of the variable; that is, the
occurrence closest to the bottom of the display that you can scroll.
v If the table has keys, the values for the keys in the added row must be different
from those in all the existing rows when you leave the Add Row option.
Otherwise, a message is displayed and the row is displayed again so you can
change the keys.
v Blank save names are ignored and do not need to be deleted, even if data is left
in the value.
v Hexadecimal data that usually cannot be displayed is converted to characters
that can be displayed or is typed by using the form:
X’nnnnnnnn’
where:
n An integer 0–9 or an alphabetic character A–F. There must be an even
number of characters within the quotation marks.
v Variables defined with the VDEFINE service as non-character are shown in
converted form; do not change them by using the hexadecimal representation. A
format or length error causes an error message to be displayed when you use
the END command.
Add Row Commands: The Add row option uses the CANCEL, END, and
LOCATE commands, and the D (delete), I (insert), and R (repeat) Dialog Test line
commands described in “Commands” on page 309. Inserted and repeated lines
always have a type of S because you can add only save variables to a row of an
existing table. Also, you can delete only save variables.
5—Display structure
When you select the Display structure option on the Tables panel, you are shown a
display of the table structure for the table specified in the Table Name field. You
can scroll this display (Figure 201 on page 333) using the scroll commands. The
table name appears in the panel header.
Option ===> 7
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Display Structure Command: The KEYS and NAMES lists can be scrolled, and
you can use the LOCATE command to find a specific variable name. See “Finding
a Character String” on page 311 for information about its use.
6—Display status
If you select the Display status option from the Tables panel, one of two data
information panels is displayed for the table specified in the Table Name field. The
information reflects all operations using the specified table, including those done at
your request by the Tables options under Dialog Test.
Table Not Open: If the table is not open for your user ID, you are shown a Status
of Table panel (Figure 202 on page 334) with the value NOT OPEN in the Status
for this screen field.
Option ===> 7
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Figure 202. Status of Table Panel with Table Not Open (ISPYTPS1)
The Modify row option on the Tables panel allows you to change a key of a keyed
table by adding the new row and deleting the old row. The row counts thus reflect
this processing when changing a key value.
Table Open: If the table is open for your user ID, you are shown a Status of
Table panel (Figure 203) with the value OPEN in the Status for this screen field.
Option ===> 7
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
Last modified by
User ID of the user who last changed the table.
Original row count
The number of rows that were added to a newly created table
before closing the table for the first time.
Current row count
The number of rows currently in the table.
Modified row count
The number of rows in the table that have been changed at least
once. A row that has been added to an existing table is also
considered a changed row.
Update count Number of times the table has been modified. One or more
updates during any table open or close sequence increments this
counter by one.
Virtual storage
The number of bytes of virtual storage required by the table.
The Modify row option on the Tables panel allows you to change a key of a keyed
table by adding the new row and deleting the old row. The row counts thus reflect
this processing when changing a key value.
You can use all the Browse commands, except BROWSE, while looking at the ISPF
log.
Each type of entry follows the format of other log entries: a short summary on the
left, and a detailed entry on the right.
The detailed section of the log entries contains an image of the service call and the
parameters used to call that service, using two lines if necessary. For example:
DISPLAY
. .. BEGIN ... TEST - DISPLAY PANEL(XYZ)
.
.
DISPLAY .. END.. ... TEST - DISPLAY PANEL(XYZ)
..RETURN CODE (0)
There can be many log entries between the begin and end entries. For example,
any active variable traces can cause log entries during a SELECT trace.
You should note the following about the service call image:
v The image is truncated after the second line.
v ISPEXEC calls are shown as typed in the dialog.
v ISPLINK and ISPLNK calls (except for the ISREDIT service) are displayed with
their parameter values separated by commas. Name-lists are shown as typed in
the dialog, in either string or structure format. Structure format includes the
count, element length, and list of names. For a variable services parameter
whose context is defined by the name-list parameter on the service call, the first
four bytes of the parameter value are displayed in hexadecimal format
(X’nnnnnnnn’).
v Dialog Test calls are shown using the command call format without the
ISPEXEC prefix.
The current value of the variable is printed in the detail section of the log entry
and can span two lines. For example:
LIB1.... POOL(P) .... - VALUE(FLAG)
...GET by EDIT -
If the variable value contains characters that cannot be displayed, the value is
displayed in hexadecimal format (X’nnnnnnnn’).
Figure 205 on page 339 shows the Invoke Dialog Service panel.
=> rempop
=> addpop
=> ispexec display
=> ispexec display panel(sample)
=>
=>
=>
=>
=>
=>
Command ===>
F1=Help F2=Split F3=Exit F4=Expand F5=Rfind F6=Resize
F7=Backward F8=Forward F9=Swap F10=Actions F12=Cancel
or
===> ISPEXEC DISPLAY PANEL(XYZ)
The service is called when you press the Enter key. You are informed of the
service’s completion and return code.
You can call any dialog service that is valid in the command environment except
CONTROL at a breakpoint or before calling a function.
The Invoke Dialog Service panel has a saved command area (the bottom portion of
the screen) that contains a list of up to 10 commands that you have saved. These
commands are point-and-shoot fields. The mode you specify from the Mode
pull-down menu on the action bar determines what happens when you select a
command.
Note: The Invoke Dialog Service panel action bar contains three pull-down choices
that let you control the saved command area.
v List
v Mode
v Functions.
Menu For more information, see the section on the Menu Action Bar Choice in
the ISPF User Interface chapter of the ISPF User’s Guide Volume I.
List The List pull-down offers you the following choices:
Note: The current setting will be shown as an unavailable choice; that is, it
will display in blue (the default) with an asterisk as the first digit of
the selection number (if you are running in GUI mode, the choice
will be grayed).
Update On Makes the list of commands in the saved command area
live; that is, new commands are appended to the list
automatically.
Update Off Makes the list of commands in the saved command area
static; that is, new commands are not appended to the list
automatically.
Mode The Mode pull-down offers you the following choices:
Note: The current setting will be shown as an unavailable choice; that is, it
will display in blue (the default) with an asterisk as the first digit of
the selection number (if you are running in GUI mode, the choice
will be grayed).
Retrieve Allows commands to be retrieved from the saved
command area and placed on the TSO Command Entry
field (==>) so that you can edit them before they are
executed. This mode is the default.
Execute Allows commands to be retrieved from the saved
command area and executed in one step.
Delete Allows you to delete commands from the saved command
area without executing the commands. Place the cursor on
the command to be deleted and press Enter. The command
will be blanked out.
Functions
The Functions pull-down offers you the following choice:
Note: The choice is unavailable when you initially enter the panel and
after you compress the list; that is, it will display in blue (the
default) with an asterisk as the first digit of the selection number (if
you are running in GUI mode, the choice will be grayed).
Compress List Compresses the saved command area by removing deleted
entries.
Utilities
For more information, see the section on the Utilities Action Bar Choice in
the ISPF User Interface chapter of the ISPF User’s Guide Volume I.
Help The Help pull-down offers you the following choices:
1 General
2 General Dialog Test
Since tracing can degrade dialog performance and create large amounts of output,
you should be careful in setting the scope of trace definitions.
When you select this option, a selection panel is displayed (Figure 207 on page
342) on which you can show the type of trace you want to define.
Option ===> 7
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
The following sections describe the options shown at the top of the Traces panel.
1—Function Traces
The Function Traces option on the Traces panel is used to establish criteria for
recording the names of dialog service calls, the service parameters, and return code
in the ISPF log. If either a dialog or Dialog Test processing causes a service call,
that call is recorded in the trace. An example of Dialog Test processing that causes
a service call is the use of the Panels option (7.2) to display a panel. Whenever a
new application or function causes data to be recorded, a header is placed in the
trace.
When you select the Function Traces option, you are shown a panel that you can
scroll (Figure 208 on page 343). The pop-up window can also be resized using the
RESIZE command. The panel lists all currently defined function traces.
You can add, delete, and change function trace definitions by using this panel,
either before calling a function or at a breakpoint.
Each line defines a function trace, showing a line command area and the following
fields:
Function
The name of the user function that should contain the trace, or ALL to
trace every dialog function. Initially, ALL is presented on the display but is
not started. Change the NO to a YES in the Active column to start such a
trace. If you want to trace a function whose name is ALL, enclose the
name in single quotes to distinguish it; that is, type ’ALL’, not ALL.
Active Whether the trace is to be active now:
YES The trace is currently active.
NO The trace is currently not active.
Blank The trace is currently active.
Dialog services to be traced
Names of dialog services to be traced. No entry in this field shows all calls
to dialog services for the function are to be traced.
All function traces exist until you leave Dialog Test, or until you delete them from
this panel. Enter new information by typing over the existing data. The
underscores are pad characters to show the starting and ending positions for each
field; you do not need to blank them out. You can create several function traces
before you press the Enter key.
During dialog processing, to determine whether the criteria for a function trace
have been met, Dialog Test processes a logical AND of the Function, Active, and
Dialog services fields specified for that function trace. Dialog Test also processes a
logical OR within the Dialog services field to determine whether a particular
dialog service has been matched. Therefore, if you want more than one trace for a
function, you should create multiple rows.
2—Variable Traces
The Variable Traces option on the Traces panel is used to establish criteria for
recording variable usage. A variable’s usage is recorded if an ISPF service is
directly asked to operate on the variable (such as VGET, VPUT, and VCOPY), or if
an ISPF service is indirectly asked to operate on the variable (such as DISPLAY).
Variables changed under the Variables option (7.3) are also recorded if the trace
specifications are met.
When you select the Variable Traces option, you are shown a display that you can
scroll (Figure 209). The pop-up window can also be resized using the RESIZE
command. The display lists all currently defined variable traces. You can add,
delete, and change variable trace definitions at a breakpoint, or by using this panel
before calling a function.
Each line defines a variable trace, showing a line command area and the following
fields:
Variable Name of the variable to be traced, or ALL to show tracing of all
variables. Initially, ALL is presented on the display but is not
started. Change the NO in the Active column to YES to start such a
trace. If you want to trace a variable whose name is ALL, enclose
that name in single quotes to distinguish it; that is, type ’ALL’, not
ALL.
Pool Pool of interest for variable tracing:
F Function variable pool.
S Shared variable pool.
P Profile variable pool.
344 z/OS V1R6.0 ISPF User’s Guide Vol II
Traces (Option 7.7)
All variable trace definitions exist until you leave Dialog Test, or until you delete
them from this panel. Enter new information by typing over the existing data. The
underscores are pad characters to show the start and end of each field; you do not
need to blank them out. You can create several variable traces before you press the
Enter key.
During dialog processing, to determine whether the criteria for a variable trace
have been met, Dialog Test processes a logical AND of the Variable, Pool,
Operation, Function, and Active fields specified for that variable trace. Therefore, if
you want more than one trace for a variable, you should create multiple rows.
Along with several menu bar items common across ISPF Version 4.1, the
Breakpoints panel has added the Qualify pull-down. You can now display the
qualification parameter values from the Breakpoints panel in two ways:
v Enter the QUAL primary command
v Select the Qualifications... choice from the Qualify pull-down.
The Function and Active columns are overlaid with a column of data titled
Qualification Parameter Values; this column was logically off the screen to the right
of the first Breakpoints panel. To resume the format of the Breakpoints panel, you
can do one of the following:
v Enter the RESUME primary command
v Select the Breakpoints... choice from the Qualify pull-down.
Specifying Breakpoints
When you select the Breakpoints option, you are shown a display that you can
scroll (Figure 210). The pop-up window can also be resized using the RESIZE
command. The display lists all currently defined breakpoints for this session. You
can use this panel to add, delete, or change breakpoint definitions, either before
calling a function or at a breakpoint.
4 Qualification Panel
5 Line Commands
6 Primary Commands
7 Usage Notes
8 General Dialog Test
All input fields contain underscores. Empty lines are added to the first display to
fill up the screen. If you delete all the lines used for defining breakpoints, the
display is automatically refreshed with enough empty lines to fill the screen again.
All breakpoints exist until you end or cancel your Dialog Test session, or until you
delete them from this panel. Enter new information by typing over the existing
data. The underscores are pad characters to show the starting and ending positions
for each field; you do not need to blank them out. You can create several
breakpoints before you press the Enter key.
Breakpoints Commands
From the Breakpoints panel, you can use the CANCEL, END, LOCATE, QUAL,
and RESUME commands, and the D (delete), I (insert), and R (repeat) Dialog Test
line commands described in “Commands” on page 309.
The Breakpoints panel with the Qualification parameter values field is displayed
(Figure 211 on page 348) if you enter the QUAL primary command on the first part
Chapter 9. Dialog Test (Option 7) 347
Breakpoints (Option 7.8)
of the Breakpoints panel or if you select the Qualifications choice from the Qualify
pull-down. The Function and Active columns are overlaid with a column of data
titled Qualification parameter values; this column was logically off the screen to
the right of the first Breakpoints panel. To resume the format of the Breakpoints
panel, use the RESUME primary command or select the Breakpoints choice from
the Qualify pull-down.
The lines on the Breakpoints panel with qualification parameter values correspond
to the lines on the first Breakpoints panel; “Specifying Breakpoints” on page 346
describes the Service and When fields. In the Qualification parameter values field,
you can enter any combination of the following for all services except SELECT:
v One or more parameter values, separated by blanks, that the dialog passes to the
service. No order is implied by the specification of the parameter values.
For example, if you want a breakpoint to occur when message ABC0001 is
included on a DISPLAY service request, specify ABC0001. If the breakpoint
should occur only when message ABC0001 and panel XYZ are both included,
specify ABC0001 XYZ.
v One or more command call keywords, separated by blanks, that have values that
are not blank when a dialog calls the service. For ISPLINK or ISPLNK calls, the
keywords matching the calling sequence parameter positions are used.
For example, if you want a breakpoint to occur whenever the DISPLAY service
is called with a message, then specify MSG.
For ISPF’s SELECT and ISREDIT services, you can enter one or more parameter
strings that would be entered on these two service calls. A parameter string is a
series of characters delimited by a blank, a comma, a single quotation mark, or a
left or right parenthesis.
then all or any of the following strings can be used: SELECT, PGM, ABC, 1, 2, 3, 5, 6.
All line commands and change capabilities are still available on the Breakpoints
panel with qualification parameter values.
During dialog processing, to determine whether the criteria for a breakpoint have
been met, Dialog Test processes a logical AND of the Service, When, Function,
Active, and Qualification fields specified for that breakpoint. Therefore, if you
want more than one breakpoint for an ISPF service, you should create multiple
rows.
When you use the Breakpoints option (7.8), be aware of the following items:
Qualification
If you plan to qualify several breakpoints, it can be more efficient to
specify all breakpoint data on the Breakpoints panel with qualification
parameter values.
END command
You can use the END primary command from either the first Breakpoints
panel or the Breakpoints panel with qualification parameter values.
Input errors
You must correct input errors before leaving any display using the END,
QUAL, or RESUME command. You can use the CANCEL command to end
the Breakpoints option, even if input errors remain on the display.
Syntax checking
A dialog service call must pass a basic syntax check before a breakpoint is
honored.
Control display
If any CONTROL service settings for DISPLAY LINE or DISPLAY SM
(Session Manager) were in effect before the breakpoint, such settings are
lost.
Finding a Breakpoint
If you call a dialog function or selection panel and find a breakpoint, the
Breakpoint Primary Option Panel is displayed. Figure 212 on page 350 shows this
selection panel at a breakpoint just after the ISPF DISPLAY service was called
while processing the TEST function in application PAY.
Like the Dialog Test Primary Option Panel, the Breakpoint Primary Option Panel
allows you to use the RETURN command from any one of the selected test options
to display the Breakpoint Primary Option Panel again. At the Breakpoint Primary
Option Panel, the END and RETURN commands have no effect. You must use the
Go option (G) to end processing at this breakpoint and continue processing the
dialog being tested, or the Cancel option (C) to cancel the Dialog Test option (7).
This protects against inadvertent loss of data.
The Breakpoint Primary Option Panel contains all the options of the Dialog Test
Primary Option Panel except Exit (7.x) and, as such, presents all but one of the
Dialog Test functions to you.
This panel also contains two options not shown on the Dialog Test Primary Option
Panel: Go (G) and Cancel (C). When a breakpoint occurs, these options allow you
to continue processing or stop processing, respectively:
G The Go option continues dialog processing from a breakpoint. The user
dialog resumes processing from the point at which it was suspended.
C The Cancel option ends dialog testing and displays the first primary option
panel you displayed at the beginning of your ISPF session again. All trace
and breakpoint definitions are lost when you leave Dialog Test.
When a user dialog finds a breakpoint, the current dialog environment is saved.
When you select the Go option, the environment is restored, except for the
following:
v If you change variable, table, and file tailoring data at a breakpoint, these actions
are an extension of the suspended dialog; it is as though the dialog had taken all
the actions itself during processing.
v If you change the service return code on the Breakpoint Primary Option Panel,
the new return code is passed back to the dialog as though the service had set
the new return code itself.
v If you process the PANELID command at the breakpoint, the last setting for
displaying panel identifiers is retained.
v If any CONTROL service settings for DISPLAY LINE or DISPLAY SM (Session
Manager) were in effect before the breakpoint, such settings are lost.
Note that the manipulation of one dialog part can cause a change to another dialog
part. For example, if a panel is displayed, variables can be set.
All trace and breakpoint definitions are lost if you select the Cancel option.
The Breakpoint Primary Option Panel also displays the following information:
AFTER or BEFORE
An indication of whether the dialog has been suspended after or before the
service has processed.
Service Name
The name of the service at which the dialog has been suspended. In
Figure 212 on page 350, the service name is DISPLAY.
Current status:
The application’s current status when the breakpoint occurred. The
following fields show this status:
Application
The application identifier of the suspended user dialog.
Function
The program or command name of the suspended user dialog.
Return code
The dialog service return code. This field is displayed only if the
breakpoint occurs after the dialog service has processed. The
Return code field is modifiable; its value is passed back to the
dialog (as the service’s) when you select the Go option. This helps
test dialog error handling.
Breakpoint
One scrollable line showing an image of the dialog service call.
Place the cursor over the image and use LEFT, RIGHT, and
EXPAND functions to scroll the area. < and > appear below the
line to indicate in which direction more data may be available. A
maximum of 2048 characters may be displayed.
ISPEXEC calls are shown as typed.
ISPLINK (ISPLNK) calls are displayed with their parameter values
separated by commas. Name-lists are shown as typed in the dialog,
in string format or in structure format. Structure format includes
the count, element length, and list of names. For variable services
parameters whose context is defined by the name-list parameter on
the service call (for example, the variable value areas for a
VDEFINE), the first four bytes of the parameter value are
displayed in hexadecimal format (X’nnnnnnnn’).
ISPEXEC calls from a program are the same as ISPEXEC calls from
a command except that ISPEXEC is not displayed.
────────────────────────────
│ ISPF Dialog Test │
────────────────────────────
This tutorial provides information about the features and operation of Dialog
Test.
The Dialog Test tutorial consists of two parts: one describes the Dialog Test
option, as selected from the ISPF Primary Option Panel, and the other
describes the Dialog Test facilities available when a user dialog encounters a
"breakpoint" in its processing.
Beginning users should review the Dialog Test Option topic first.
The default function key command assignments for a terminal with 12 function
keys are shown at the bottom of the screen if you enter the PFSHOW command.
When you select one of these products, ISPF tries to call it. However, the only way
ISPF can determine whether a product is installed and available is to check for the
existence of a single product-related panel in the panel library concatenation. No
other check is made to ensure that the product is correctly installed or that it is
completely available to you.
The names of the products on this panel are point-and-shoot fields. For more
information on point-and-shoot fields, see the ISPF User Interface chapter in the
ISPF User’s Guide Volume I.
If SCLM does not appear on any of your menu panels or on your Menu pull-down,
you can still access it by typing TSO SCLM on any ISPF command line, then
pressing Enter. If SCLM is available to your terminal session, the SCLM Main
Menu is displayed. If SCLM is not available on your system, a panel (ISRNOSLM)
is displayed to inform you that SCLM is not available to your terminal session.
For more information about SCLM, refer to the ISPF SCLM manuals.
Option ===>
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
The option names on this panel are point-and-shoot fields. See the Point-and-Shoot
Text Fields section of the ISPF User Interface chapter in the ISPF User’s Guide
Volume I for more information.
SCLM Overview
SCLM is a library facility that supports projects in developing complex software
applications. It does this by providing software configuration and library
management support. SCLM supports the software development cycle of an
application from the program design phase to release of the final product.
SCLM provides the following facilities for automating software configuration and
library management tasks:
Project Definition Establishes the database.
Edit Uses the ISPF editor to create and modify the
software components.
Build Integrates the software components.
Promote Moves software components through the library
hierarchy.
Utilities Maintain the database.
Reports Generate information about the build and promote
activities, and about the contents of the database.
Interactive dialogs, batch interfaces, and callable services provide access to the
functions and capabilities of SCLM. These functions support the routine use of
SCLM by:
v Allowing programmers to use the ISPF editor to create and modify software
components
v Providing automated draw down and lockout functions without requiring
special customizing to suit a particular installation.
There is a fast path system command for starting the Workplace. Type ISPFWORK
on any ISPF command line and you are taken to the Workplace entry panel.
You can display the Workplace in GUI mode as well as standard mode. See
“Workstation Connection” on page 67 for information about how to start GUI
mode for ISPF. All of the screens that appear in this chapter are shown in their
standard mode.
Selecting Objects
The first step in using the Workplace to perform ISPF functions is to specify the
particular object that you want to perform an action on, for example, a sequential
data set ’YOURID.SOURCE.DATA’. Object specification takes place on the
Workplace entry panel.
The Library View panel has the words “Library View” as a heading just above the
referral lists in the lower portion of the screen. This view enables you to work with
ISPF library concatenations and library lists.
The Data Set View panel has the words “Data Set View” as a heading just above
the referral lists in the lower portion of the screen. This view enables you to work
with data set lists, sequential files, or single partitioned data sets. You can choose
to work with either entry panel view by using the command LISTVIEW, or the
function key ChgView (F11) to toggle between the two panels.
Library View
You use the Library View to work with a ISPF library concatenations. The panel
that appears in Figure 216 is the Library View entry panel for the Workplace.
ISPF Library
Project . . .
Group . . . . . . . . . . . . .
Type . . . . . SOURCE
Member . . . . (Blank or pattern for member action list)
When using this Workplace entry panel, you can select a data set or a group of
data sets to work with in one of the following ways:
v Fill in the ISPF Library fields. These fields are used the same way as they are on
other ISPF panels. You can use the traditional method of selecting a data set by
entering its Project, Group, Type, and Member names in the ISPF Library fields.
Omitting the Member name gives you a list of members to choose from.
v Select an object or list of objects using “ISPF Referral lists for object retrieval”.
See “ISPF Referral Lists for Object Retrieval” on page 361 for more information.
You can access personal and reference lists, and then select libraries from these
lists.
Note: Catalog, DSLIST, Volume information, Print volume, and Workstation file
actions, are only available from the Data Set View.
The panel that appears in Figure 217 on page 361 is the Data Set View entry panel
for the Workplace.
When using this Workplace entry panel, you can select a data set or a group of
data sets to work with in one of the following ways:
v You can use the traditional method of selecting a data set by entering its name
in the Object Name field. For example, enter ’YOURID.SOURCE.DATA’ to act
upon a data set on the host, or D:\YOUR.FIL to act upon a workstation file
(perhaps to edit it using the PDF editor).
v Select an object or list of objects using “ISPF Referral lists for object retrieval”.
You can access personal and reference lists, and select data sets, libraries,
workstation files, VSAM files, and data set levels from each list.
All data sets and libraries referenced during an ISPF session are appended to the
reference lists. You can use the input fields next to the referral lists to access a
referral data set in one of the following ways:
v Entering a slash (/) in this field causes the personal data set list or library list
(depending on the selected view) to be displayed.
v Type DL in the input field and press Enter. This builds a DSLIST based on entries
in the personal data set list, personal library lists, or Reflists.
v Enter a library entry number (from 1 to 8). If you know the list numbers of your
libraries, for example, your panels library is number 1, you can type the number
in this field and press Enter. ISPF retrieves the respective library entry from the
library reference list.
v Enter a data set entry number (from 1 to 30). If you know the order of your data
sets, you can type the number in this field and press Enter. ISPF retrieves the
respective data set entry from the data set reference list.
Specifying Actions
After you select the object you want to work with, choose the action to perform on
it. You can select an action by making a choice on an action bar or by using a
command.
File
The File action bar choice enables you to manipulate files. The pull-down choices
for File are:
Choice Description
List Displays a pop-up menu that enables you to choose either a member list, a
data set list list, a list of personal data set lists or a list of personal library lists.
You can perform any of the File actions except DSLIST against the
resulting member list.
Member list
Displays a list of members for a partitioned data set. To display a
member list:
1. Type the library or data set information in the appropriate
fields of the Workplace entry panel (library view).
2. Specify blank or a pattern for the member name to display a
member list.
3. Select the List action from the File action bar choice.
4. Select “Member list” from the List Action prompt panel.
2. Select Personal Data Set List from the List Action prompt panel.
You can perform this action from either view of the Workplace
entry panel.
Personal Library lists
Displays a list of your personal library lists. All valid personal list
actions can be performed against any selected personal list. The
personal library list you used most recently is the current active
list. The currently active list cannot be directly deleted from the list
dialog, however all other list actions are valid. To list your
personal library lists:
1. Select the List action from the File action bar choice.
2. Select Personal Library List from the List Action prompt panel.
You can perform this action from either view of the Workplace
entry panel.
Edit Starts Edit action for a member or a sequential file. The Edit action prompt
panel is presented when you choose the Edit pull-down choice on the
action bar. Select a file type and an editor and press Enter. The Edit
function is used to edit a member of a partitioned data set, a sequential
data set, or a workstation file.
Type of File
Select the type of file you want to edit.
1. Host File
Edit a host file using ISPF Edit or a workstation-defined
editor. The selection of host or workstation editors is based
on the Editor Choice option setting on the Edit Entry
panel. To start the member list function, enter a pattern or
leave the member field blank on the Workplace entry
panel. To edit a single member on the host:
1. Type the library or data set information in the
appropriate fields of the Workplace entry panel.
2. Type the member name in the member field (for library
view) or in parentheses after the data set name (for
data set view).
3. Select Edit under the File action bar choice.
4. Select Host File and ISPF Editor on the Edit Action
prompt panel.
1. Type the file path and name in the Object name field of
the Workstation entry panel (data set view).
2. Select View from the File action bar choice.
3. Select Workstation File and Workstation View from the
View Action prompt panel.
View Choice
1. ISPF View
Selects the ISPF view function.
2. Workstation View
Selects the workstation editor or browser.
Browse
Starts Browse action for a member or a sequential file.
If you do not specify a member name or if you specify a pattern and the
specified data set is a PDS, a member list is displayed. Select a member to
Browse by typing s next to the member name.
To browse a single member:
1. Type the library or data set information in the appropriate fields of the
ISPF Workplace panel.
2. Type the member name in the member field (for ISPF library view) or
in parentheses after the data set name (for data set view).
3. Select Browse from the File action bar choice.
Delete Displays a pop-up prompt window with member or data set as the choices.
If you specify an asterisk (*) as the member name, all members of the PDS
are deleted without a member list being displayed.
If you do not specify a member name or if you specify a pattern and the
specified data set is a PDS, a member list is displayed. Select members to
delete by typing s next to the member name.
Note: You can change how member name patterns are handled in your
Workplace Settings. See “Show status for M,C,D,G actions” on page
384 for more information.
1. Type the library or data set information in the appropriate fields of the
ISPF Workplace panel.
2. Type the member name in the member field (for ISPF library view) or
in parentheses after the data set name (for data set view).
3. Select Rename under the File action bar choice for member rename.
Note: You can change how member name patterns are handled in your
Workplace Settings. See “Show status for M,C,D,G actions” on page
384 for more information.
Note: You can change how member name patterns are handled in your
Workplace Settings. See “Show status for M,C,D,G actions” on page
384 for more information.
Reset Starts reset action for a member. A Reset prompt panel is presented for the
member.
If you specify an asterisk (*) as the member name, all members of the PDS
are reset without a member list being displayed.
If you do not specify a member name or if you specify a pattern and the
specified data set is a PDS, a member list is displayed. Select members to
reset by typing s next to the member name.
Note: You can change how member name patterns are handled in your
Workplace Settings. See “Show status for M,C,D,G actions” on page
384 for more information.
2. Type the member name in the member field (for ISPF library view) or
in parentheses after data set name (for data set view).
3. Select Submit from the File action bar choice.
Print The Print selection enables you to print information. The pull-down
choices on the Print action prompt panel are:
Data Set
Prints the entire data set. To print a data set:
1. Type the data set name in the Object name field (for the data
set view) or enter an ISPF library name in the ISPF Library
fields (for the library view).
2. Select the Print action from the File action bar choice.
3. Select Data Set from the Print Action prompt panel.
Data Set index
Prints the data set index for the selected data set. To print a data
set index:
1. Type the data set name in the Object name field or type an
ISPF library name in the ISPF Library fields.
2. Select the Print action from the File action bar choice.
3. Select Data Set Index from the Print Action prompt panel.
Data Set List
Prints the list of data sets for the selected data set name level. To
print a data set list:
1. Type a data set level, or optionally a volume serial, in the
appropriate fields on the ISPF Workplace panel.
2. Select Print from the File action bar choice.
3. Select Data set List from the Print Action prompt prompt panel.
VTOC Prints the VTOC information for the selected volume. To print a
VTOC summary:
1. Type a volume serial in the proper field on the ISPF Workplace
panel.
2. Select Print from the File action bar choice.
3. Select VTOC from the Print Action prompt panel.
Member
Prints the selected member. To print a member:
1. Type the data set name in the Object name field or type an
ISPF library name in the ISPF Library fields.
2. Select the Print action from the File action bar choice.
3. Select Member from the Print Action prompt panel.
Command
Enables you to enter TSO, Workstation, or ISPF commands. You are
prompted to choose between types of commands. The pull-down choices
on the Command prompt are:
TSO Cmd
The TSO Cmd action is used to run a TSO command, passing the
data set and member name and any additional parameters to the
TSO command entered. To run a TSO command against a single
member, fill in the following fields of the ISPF Workplace panel:
1. Type the library or data set information in the appropriate
fields.
2. Type the member name in the member field (for ISPF library
view) or in parentheses after the data set name (for data set
view).
View
The View action bar choice displays the object views that are available to you. The
currently selected view is unavailable.
Library View Changes the current view to reference library list, personal library
lists, and ISPF Library view.
To change to the ISPF Library view:
1. Select the View action bar choice.
2. Select Library View from the pull-down menu.
By name Changes the current view of the personal list by sorting on the
name field.
By description
Changes the current view of the personal list by sorting on the
description field.
By created Changes the current view of the personal list by sorting on the
created field.
By referenced Changes the current view of the personal list by sorting on the
referenced field.
Options
The Options action bar choice displays the settings available. The pull-down
choices for Options are:
Choice Description
Workplace Settings
Displays the Workplace Settings panel. See “Changing Workplace
Settings” on page 383 for more information.
ISPF Settings Displays the ISPF Settings panel. See Chapter 2, “Settings (Option
0),” on page 25 for more information.
CUA Attributes
Starts the ISPF CUA Attribute Change Utility dialog. See “CUA
Attributes” on page 62 for more information.
Keylists Starts the ISPF Keylist Utility dialog. See “Working with Function
Keys and Keylists (The Function Keys Action Bar Choice)” on page
41 for more information.
Point-and-Shoot
Starts the ISPF CUA Attribute Change Utility dialog indexed to the
point-and-shoot entry. See “CUA Attributes” on page 62 for more
information.
Colors Starts the ISPF Global Color Change Utility dialog. See “Changing
Default Colors (The Colors Action Bar Choice)” on page 57 for
more information.
Space
The Space action bar choice enables you to create and maintain data sets. The
pull-down choices available for Space are:
Choice Description
Allocate Displays a pop-up menu for the allocate action. The choices on the
prompt are:
Data Set
The allocate action is used to allocate a partitioned or
sequential data set. To allocate a data set:
1. Type the data set name in the Object name field or type
an ISPF library name in the ISPF Library fields.
SuperC
The SuperC action bar choice gives you access to SuperC compare and search
dialogs for your data sets. The data set you specify on the Workplace panel is
automatically filled in for you in the Superc dialog you choose. For more
information, see “SuperC Utility (Option 3.12)” on page 210.
Test
The Test action bar choice gives you access to the ISPF services that help you test
dialogs, such as Chapter 9, “Dialog Test (Option 7),” on page 305. For more
information, refer to the ISPF Dialog Developer’s Guide and Reference, and the ISPF
Edit and Edit Macros manual.
Choice Description
Functions Displays the Dialog Test Function/Selection panel. Select the
Functions action from the Test action bar choice. For more
information, see “Functions (Option 7.1)” on page 313.
Panels Displays the Dialog Test Display panel. Select the Panels action
from the Test action bar choice. For more information, see “Panels
(Option 7.2)” on page 316.
Variables Displays the Dialog Test Variables panel. Select the Variables action
from the Test action bar choice. For more information, see
“Variables (Option 7.3)” on page 319.
Tables Displays the Dialog Test Tables panel. Select the Tables action from
the Test action bar choice. For more information, see “Tables
(Option 7.4)” on page 324.
Log Displays the ISPF Transaction Log panel. Select the Log action from
the Test action bar choice. For more information, see “Log (Option
7.5)” on page 336.
Services Displays the Invoke Dialog Service panel. Select the Services action
from the Test action bar choice. For more information, see “Dialog
Services (Option 7.6)” on page 338.
Traces Displays the Dialog Test Traces panel. Select the Traces action from
the Test action bar choice. For more information, see “Traces
(Option 7.7)” on page 341.
Break Points Displays the Dialog Test Breakpoints panel. Select the Break Points
action from the Test action bar choice. For more information, see
“Breakpoints (Option 7.8)” on page 345.
Dialog Test Displays the Dialog Test Primary Option panel. Select the Dialog
Test action from the Test action bar choice. For more information,
see Chapter 9, “Dialog Test (Option 7),” on page 305.
Dialog Test appl ID
Displays the Dialog Test Application ID panel for changing the
Dialog Test application ID. Select the Dialog Test appl ID action
from the Test action bar choice.
Help
The Help action bar choice provides access to the program tutorials.
For more information about how the Reset statistics option works, see “Reset ISPF
Statistics Utility (Option 3.5)” on page 183. You can set the following items from
this window:
Options
Select 1 to Reset ISPF statistics, or 2 to Delete ISPF statistics.
New Userid
Sets the ID field in the statistics. If you want to change the ID the statistics
are kept under, enter the new ID here. If you do not specify a new version
number, this field is required to be filled in.
New Version
Enter a number here is you want to change the version number. This field
is required if you do not enter a new userid. It is ignored if you have
chosen the delete action.
New Mod
Use a slash (/) to select this option. Deselect this option if you do not want
to reset the modification level. A new version number is required to reset
the modification level.
TSO Command
Figure 219 on page 375 shows the pop-up prompt window that appears when you
choose Command, from the File action bar choice, then select TSO Command from
the Command Action prompt panel.
WS Command
Figure 220 on page 376 shows the pop-up prompt window that appears when you
choose Command, from the File action bar choice, then select WS Command from
the Command Action prompt panel. You must have a workstation connection in
place in order to use WS commands.
===>
The ISPF Command Shell option enables you to run TSO commands, CLISTs, and
REXX execs under ISPF. This panel has one input field. Type the command and its
parameters into the input field, leaving at least one space between the command
name and the first parameter. The input field continues for two full lines below the
start of the input field. The maximum number of characters that you can enter is
234. For example:
Enter TSO or Work Station commands below
===> SEND ’THIS MESSAGE DEMONSTRATES THAT A TSO COMMAND ENTERED UNDER
ISPF CAN EXCEED ONE LINE ON THE 3270’ USER(ALICE)
You can also enter ISPF commands, such as END or RETURN, in this field.
Note: If you enter HELP or CANCEL, it is interpreted as the ISPF Help or Cancel
command. To issue TSO Help, enter:
===> TSO HELP xxxxx
The ISPF command shell option enables you to enter most TSO commands under
ISPF. Following is a list of commands that are not supported:
v LOGON
v LOGOFF
v ISPSTART, PDF, and ISPF
v TEST
v Commands that you are restricted from using by TSO or PCF
v Commands requiring large parameter lists (234 characters is the maximum
allowed, including command name)
You can run command procedures under ISPF, subject to the following restrictions:
v CLISTs and execs must not invoke restricted commands listed previously.
After you type a command in the input field, press ENTER to start the command.
If you are not operating in Session Manager mode, the cursor is positioned below
the command input field. Line-at-a-time I/O from the command, if any, starts at
the cursor position. When the command finishes, three asterisks (***) may appear
on the screen. To return to ISPF full screen mode, press ENTER.
The ISPF command shell panel is then redisplayed with the command you entered
displayed in the command list (unless you entered the TSO or WS prefix, or List
mode is set to update off).
Move or Copy
Figure 222 shows the pop-up prompt window that appears when you choose Move
from the File action bar, after you choose a member to work with. The panel that
appears when you choose Copy is similar to this one.
RefList Help
──────────────────────────────────────────────────────────────────────────────
MOVE Entry Panel
More: +
CURRENT from data set: ’MYPROJ.DEV.SOURCE(TEST)’
To Library Options:
Project . . . MYPROJ Enter "/" to select option
Group . . . . DEV _ Replace like-named members
Type . . . . SOURCE / Process member aliases
Options
Sequential Disposition Pack Option SCLM Setting
2 1. Mod 1 1. Default 3 1. SCLM
2. Old 2. Pack 2. Non-SCLM
Command ===> ________________________________________________________________
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F12=Cancel
For more information about the Move/Copy utility, see “Move/Copy Utility
(Option 3.3)” on page 142. You can set the following items from this window:
To Library
The library to which you want to move or copy the selected data.
To Other Data Set Name
The data set to which you want to move or copy the selected data.
NEW member name
If the “To” and “From” data sets are the same, you can rename the
member here.
Rename
Figure 223 shows the pop-up prompt window that appears when you choose
Rename from the File action bar, after you choose a member to work with.
You choose to rename either a data set or a member from this panel. If you choose
data set, the panel in Figure 224 on page 380 appears.
┌─────────────────────────────────────────────────────────────────────────┐
─ │ Rename Data Set │
I │ │
│ Data Set Name . . : MYPROJ.DEV.SOURCE │
D │ Volume Serial . . : MVS8WF │
│ │
│ Enter new name below: (The data set will be recataloged.) │
│ │
┌ │ ISPF Library: │
│ │ Project . . │
│ │ Group . . . │
│ │ Type . . . . SOURCE │
│ │ │
* │ Other Partitioned or Sequential Data Set: │
│ Data Set Name . . . ’MYPROJ.DEV.SOURCE’ │
│ │
│ │
│ │
│ │
│ │
│ Command ===> │
A │ F1=Help F2=Split F3=Exit F7=Backward F8=Forward │
│ F9=Swap F10=Actions F12=Cancel │
└─────────────────────────────────────────────────────────────────────────┘
New name
The name that you want to use for the renamed member.
Commands
You can use primary commands in the command area (Action line) of the
Workplace entry panels.
You must be connected to the workstation to use any workstation file actions. You
can configure your workstation editor choice by selecting the Workstation action bar
from the Edit or View entry prompt panel or from the Workplace Settings panel.
Table 24. Workstation Commands
Command Description Valid For:
A Allocate Data sets
ACTBAR or Display or do not display action bar Action prompt
NOACTBAR on panel
AP Allocate Action prompt
B Browse Members and non-PDS data sets
C Copy Members and non-PDS data sets
COLOR Global color change Action prompt
CP Command Action prompt
CUAATTR CUA attributes Action prompt
D Delete Members and non-PDS data sets
DF Delete Data sets
DL DSLIST Data set name level
DP Delete Action prompt
DVT VTOC summary Data summary
E Edit Members and non-PDS data sets
EP Edit Action prompt
G Reset member statistics Members
I Full information Data sets
ICS ISPF command shell Action prompt
ICT ISPF command table Action prompt
IP Information Action prompt
J Submit Members and non-PDS data sets
K Catalog Data sets
KEYLIST Keylist utility Action prompt
L Print data set Data sets
LOCATE, LOC, or L Find a specified referral list in the Referral lists
scrollable display of referral lists
LP List Action prompt
LV or LISTVIEW List view Action prompt
M Move Members and non-PDS data sets
ML Member list Partitioned data sets
N Rename Data sets
O Open Members and non-PDS data sets
OPD Personal data set lists Referral lists
OPL Personal library lists Referral lists
P Print Members and non-PDS data sets
┌─────────────────────────────────────────────────────────────────────────┐
│ File Defaults Colors Workstation Help │
│ ────────────────────────────────────────────────────────────────────── │
│ ISPF Workplace Settings Main │
│ │
│ General Options View Options │
│ Enter "/" to select option Data Set List View │
│ / Display Edit/View entry panel 1 1. Volume │
│ / Automatically Update reference lists 2. Space │
│ / Keep member field value 3. Attrib │
│ / Member List for M,C,D,G actions 4. Total │
│ / Show status for M,C,D,G actions │
│ / Confirm Member delete Member List View │
│ / Confirm Data Set delete 1 1. Standard │
│ / Show Workplace Action bar 2. Extended │
│ / Frame ISPF Personal list area │
│ / Smart Action Retrieve Entry Reflist Frame Char │
│ / Display Catalog Name 1 1. | (X"6A") │
│ 2. | (X"4F") │
│ │
│ Press EXIT to save settings. Press CANCEL to cancel any changes. │
│ F1=Help F2=Split F3=Exit F7=Backward F8=Forward │
│ F9=Swap F10=Actions F12=Cancel │
└─────────────────────────────────────────────────────────────────────────┘
Subtask 1
Your first step is to copy a sequential data set into a member of a concatenated
PDS.
Workplace: Use the Copy Action against the sequential data set object.
Choose the Workplace option (Option 11) on the main menu. Use the PF11 key to
toggle to the data set view. In the Workplace you have a choice of working from a
data set list or issuing commands against a single data set.
If you are list-oriented you can specify a wildcard character in the Object Name
field (such as, ’USERID.*’) to generate a data set list containing the sequential data
set.
If you prefer to specify the sequential data set directly you can type it into the
Object Name field either with or without single quotes (that is, SEQ.FILE or
’USERID.SEQ.FILE’).
Now that the Object has been specified you must specify the Action. In this
example, the action is COPY. You can do this several ways, depending on your
preferences.
v If you are in a list, you can use the CO line command to copy the data set, or
you can put a slash (/) in the line command field to be prompted with a list of
available commands to select.
v If you specified the ″from″ data set directly (not from a list) you can use the
Copy option from the File action bar choice, or you can type the C fast path
command in the Action ==> field to copy the data set.
In either case, a pop-up panel prompts you for the target data set, member name,
and other parameters.
Subtask 2
The second step is to SuperC compare one member of a concatenated PDS to
another.
Specify the ISPF library concatenation and member name of the new member you
just created by the COPY action. The following accelerated methods can be used as
alternatives to remembering and typing the input:
v You might be able to retrieve a recently referenced ISPF Library concatenation
from the REFLIST in the bottom half of the Workplace.
v You might be able to retrieve a recently referenced ISPF Library concatenation
using the recall key PF5.
v You might be able to retrieve an ISPF Library concatenation from a personal list
you previously created. These also appear in the bottom half of the Workplace.
Now that the Object has been specified you must specify the Action. The action at
this point is SuperCE. Again, specifying this action can be done several ways
depending on your preferences.
v You can use the SuperCE option from the SuperC action bar.
v You can type the ″SCE″ fast path command in the Action ==> field and press
Enter.
In either case, Workplace enters the SuperCE dialog. Note that your ISPF Library
concatenation is transferred to the correct New DSN fields in the SuperCE
concatenation panel, so you do not have to type it yourself.
After running your compare, exit the SuperC Utility to return to Workplace.
Subtask 3
The next step is to rename a member of an ISPF Library.
The ISPF library concatenation and member name of the new member you just
compared remains on the Workplace panel. Now you must specify the Rename
Action.
v Just press Enter if your default enter action is Smart Action, a mode that
analyzes the object and selects an appropriate action. Select the Workplace
Settings option from the Options action bar to view or change your defaults.
v Enter the List option from the File action bar.
v Enter the ″ML″ fast path command.
In any case, Workplace displays a pop-up panel to prompt you for the new
member name.
Subtask 4
The final step in this scenario is to change a member’s Version number in the ISPF
statistics.
The ISPF library concatenation and member name of the new member you just
compared remains on the Workplace panel. Now you must specify the Reset
Action.
In all cases, Workplace displays a pop-up panel to prompt you for Reset
parameters.
ISPF contains two utilities, SuperC (option 3.12) and SuperCE (option 3.13), that
allow you to compare data sets for differences. Also, ISPF contains two other
utilities, Search-For (option 3.14) and Search-ForE (option 3.15), that allow you to
search data sets for strings of data.
All four of these utilities combine two major components to do their respective
functions. The first component is a dialog that provides the data entry panels,
selection panels, and messages. The second component is the program module,
ISRSUPC. The CPI interface is through a standard parameter list.
You can use the SuperC program without the ISPF utilities. To do this, however,
your installation must customize a CLIST or REXX EXEC (for interactive use), or a
PROCLIB procedure (for batch processing of a catalog procedure). A sample CLIST
has been provided to show line command processing. A sample PROCLIB JCL
catalog procedure has also been provided to show batch submission. The sample
CLIST and PROCLIB JCL are located in the SAMPLIB data set as members
ISRSCLST and ISRSPROC, respectively.
Utility Differences
The standard utilities, SuperC (option 3.12) and Search-For (option 3.14), are easy
to use with somewhat reduced function. The extended utilities, SuperCE (option
3.13) and Search-ForE (option 3.15), fully exploit the SuperC program’s capabilities.
Standard Utilities
The standard utilities are useful for ordinary comparisons and searches. The
SuperC utility (option 3.12) uses a two-panel sequence: you specify the new input
data set on the first panel and the old input data set on the second. The Search-For
utility (option 3.14) uses an optional two-panel sequence: you can specify the input
data set and one search string on the first panel, and use the second panel if you
need to specify more than one search string.
You can enter additional information on these panels as they are displayed. If you
are using the SuperC utility, you can enter the name of a previously prepared
profile data set that contains additional information to specify the comparison.
Search-For does not use a profile data set. Also, Search-For finds all occurrences
without case distinction when searching for a data string.
Extended Utilities
The primary intent of the extended utilities is to provide maximum flexibility and
access to all SuperC functions. Input fields are provided to allow you to use
process options and statements. Also, the Search-ForE utility’s ASIS fields allow
you to specify mixed-case search strings.
The input data set name fields differ from standard ISPF format because Project,
Group, Type, and Member fields are not provided. Instead, you can enter input
data set names horizontally using standard TSO naming conventions. This includes
the use of a PDS member name, if desired, as part of a data set name.
The concatenation of input data sets is also different. Up to four data set names, as
opposed to the standard four ISPF library groups, can be entered as new or old
data sets. This allows data sets with the same attributes to be concatenated. For
example, PANELS and MSGS data sets could be concatenated for searching.
Besides compare functions, the SuperCE Utility panel provides access to the
Search-ForE utility (option 3.15). This gives you the added advantage of the ability
to search for a data string without having to leave SuperCE, in addition to access
to more functions than Search-For (option 3.14) provides.
Program Description
The SuperC program is a fast and versatile program that can process:
v Two sequential data sets
v Two complete partitioned data sets
v Members of two partitioned data sets
v Concatenated data sets.
In fact, any data set that can be processed by ISPF can be processed by the SuperC
program.
SuperC can compare data sets even when there are many differences and
redundant data. Some examples of redundant data are blank lines, duplicate
words, and binary data with many duplicate characters.
Unlike many compare programs, SuperC is not limited to comparing data sets on a
line-by-line basis. Instead, it allows you to choose between the following four
comparison levels. The compare type you select determines which kinds of data
differences are presented by SuperC. See “Why Compare Types May Produce
Different Comparison Results” on page 462 for more information about
comparison results.
v File comparisons produce summary information about the differences between
the data sets being compared.
v Line comparisons are record-oriented and show matching, inserted, deleted, and
reformatted lines. This level is most useful for comparing lines of program
source code. It provides the least output difference information and is least
sensitive to resynchronization.
v Word comparisons show differences between data strings that are delimited by
blanks or nonalphanumeric characters, such as commas. Matching words are
found, even if they are not on the same line. This level is most useful for
comparing text data sets.
v Byte comparisons determine byte differences. It is most useful for comparing
unformatted and machine-readable data.
The SuperC program requires only the names of the input data sets. However, the
utility you are using may require other information, such as a listing type. Also,
you can enter the following types of processing information and options on the
utility data entry panels:
v Compare type
v Listing data set name or destination
v Process options
v Statements or profile data set name
v Browse output choice.
Within these two categories, you can create many kinds of output that make it easy
to see where your data differs. To see your comparison results, you can generate
listings that show:
v An overall summary of total changes
v The actual source code where deltas (differences) were found
v The deltas plus up to 10 (the default) matching lines before and after
v The deltas plus all matching lines.
You also have a choice between listings that show differences either sequentially or
side-by-side.
In an update data set, output lines are identified and results are put in specific
columns. An update data set is especially useful as input to a user-written
application program. It allows a program to customize what you see, changing
generalized output to information that is specific to a particular application.
The SuperC utility (options 3.12, 3.13, and 3.14) CLISTs allocate or free space under
the following DDNAMEs: SYSIN, SYSIN2, OLDDD, NEWDD, OUTDD, and
DELDD.
Applications
You can use the SuperC program for many applications other than comparing two
source data sets. This section lists some specific applications for general users,
writers and editors, and programmers and systems administrators.
SuperC detects and classifies reformatted lines as special changes. You can list
these lines in the output, along with the normal insert/delete changes, or
eliminate them from the listing. Reducing the number of flagged lines may help
you focus on real, rather than cosmetic, changes.
v Determine whether two PDSs, or a concatenation of PDSs, have corresponding
like-named members.
Members absent from one data set but present in the other are listed, as is all
change activity between like-named members. The comparison can show
changes caused by creating or deleting PDS members.
the update data sets are more structured and should be easier to use as data
input. See ISPF Dialog Developer’s Guide and Reference for explanations and
examples of the update data sets.
Table 26. Summary of Process Options for Search and Compare (continued)
Valid For
Process Option Compare Type
Keyword Description FILE LINE WORD BYTE Search
5
LONGLN Long lines U U
4
LPSF List previous -search -following lines U
4
LTO List totals only U
MIXED Mixed input (single/double byte) text U U
5
NARROW Narrow (side -by -side) listing U
NOPRTCC No printer control columns U U U U U
2
NOSEQ No sequence numbers U U U
NOSUMS No summary section U U U U
REFMOVR Reformat override U
SDUPM Search duplicate members U
2
SEQ Ignore standard sequence number columns U U U
6
UPDCMS8 Update CMS8 format U
6
UPDCNTL Update control U U U
6
UPDLDEL Update long control U
6
UPDMVS8 Update MVS8 format U
6
UPDPDEL Update prefixed delta lines U
6
UPDREV Update revision U U
6
UPDREV2 Update revision (2) U U
6
UPDSEQ0 Update sequence 0 U
6
UPDSUMO Update summary only U U U
5
WIDE Wide (side -by -side) listing U
XREF Cross reference strings U
XWDCMP Extended word comparison U
7
Y2DTONLY Year 2000 Compare Dates Only U
Notes:
1. Valid for group LINE comparisons only.
2. COBOL, SEQ, and NOSEQ are mutually exclusive.
3. Not supported for PDSE data sets.
4. LMTO, LNFMTO, LPSF, and LTO are mutually exclusive.
5. LONGLN, NARROW, and WIDE are mutually exclusive.
6. All update (UPD) process options are mutually exclusive. Also, they cannot be used with the process option
Y2DTONLY.
7. Y2DTONLY is not supported for change bar listing (process option GWCBL).
The SuperC Compare process options are listed alphabetically and defined below:
ALLMEMS All members. Compare all members including alias entries. This
functions as though all directory entries were selected from a
member list.
ANYC Any case. SuperC converts the lowercase alphabetic characters (a-z)
and/or the update file for the option UPDSUMO only if there are
differences. This is useful when used in combination with
APNDLST or APNDUPD.
Valid for File, Line, Word, and Byte compare types.
DLMDUP Don’t list matching duplicate lines. SuperC omits the old data set
source lines and new data set source lines that match from the
side-by-side output listing. This reduces the redundant lines in the
side-by-side old data set source lines columns. It puts more
emphasis on the old data set changed lines and sections of
changes.
This option is valid for the Line compare type in combination with
the WIDE or NARROW process option.
DLREFM Don’t list old data set reformatted lines. This option omits
reformatted old data set lines from the output listing. They usually
appear as separate lines under new reformatted lines. Only the
new reformatted lines are listed in the output.
set with only 55 columns from each source data set. Inserted and
deleted lines are flagged and appear side-by-side in the listing
output.
This option is valid for the Line compare type.
NOPRTCC No printer control columns. SuperC generates “normal” or
NARROW listing data sets with record lengths of 133 columns, or
WIDE or LONGLN listing data sets with 203 columns. These
listings contain printer control columns and page separators.
NOPRTCC eliminates both the page separators and the control
column 1. With NOPRTCC, “normal” and NARROW listings are
132 columns, and WIDE and LONGLN listings are 202 columns.
However, initial title lines and section separators are still
generated.
This option produces a data set that is better for online “browsing”
because it does not have interspersed page separator title lines.
control records and new data set source lines. Columns 73-80 from
the old DS lines are used as references. Only fixed 80 data sets are
allowed.
SuperC may change the status of matched lines to insert/delete
pairs, enlarging the sequence number gaps of the old data set. The
CMS update data set (when properly named) can be used as input
to CMS XEDIT. For information and an example of this update
data set, see Figure 240 on page 481.
This option is valid for the Line compare type.
UPDCNTL Update control. Produces a control data set which relates matches,
inserts, deletes, reformats, and “don't process” lines (Line compare
only) using relative line numbers (for Line compare), relative word
positions (for Word compare), or relative byte offsets (for Byte
compare) within the new and old data sets. No source or data from
either input data set is included in the output data set. For
information and an example of this update data set, see
“UPDCNTL—Update Control” on page 481.
This option is valid for the Byte, Line, or Word compare types.
UPDLDEL Source data set with delta changes. UPDLDEL produces a control
data set that combines new source matched lines and changes from
the new and old source data sets. The control lines are titled as
follows:
Title Control line
*HDR1, *HDR2, and *HDR3
Header titles and data
*M- Matched line sequence header
*I- Inserted line sequence header
*I-RP Inserted line sequence header for replacement lines
*I-RF Inserted line sequence header for reformatted lines
*D- Deleted line sequence header
*D-RP Deleted line sequence header for replacement lines
*D-RF Deleted line sequence header for reformatted lines.
Header control records delimit the copied data set lines. This
allows you to quickly find changed areas. The lines are full length
records. The lines appear similar to the information on a LONG
listing. The two input data sets must have the same fixed LRECL
or each have a variable RECFM.
You should be able to edit this data set to obtain a final composite
source data set including all the change activity of two different
developers. For information and an example of this update data
set, see “UPDLDEL—Update Long Source and Delta Data Set” on
page 485.
All process statements that are shown with a Search syntax can be entered in a
statements data set and used with the Search-ForE utility (option 3.15), but not
with the Search-For utility (option 3.14).
v Stacked operands shown in brackets indicate the optional operands from which
you can select one or none.
v Stacked operands shown in braces ({ }) are required operands from which you
must select one.
v Syntax diagrams that end with an ellipsis (...) allow you to repeat operands
more than once.
v If a statement contains a KYWD operand, this keyword must precede any
repetition of the operands that follow.
The compare type that you select determines the process statements available
(Table 27).
Table 27. Summary of Process Statements for Compare and Search
Valid For
Process Statement Compare Type
Keyword Description FILE LINE WORD BYTE Search
CHNGV Change listing value U U U
CMPBOFS Compare byte offsets U
CMPCOLM Compare (search) columns: new, old, search U U U
files
CMPCOLMN Compare columns: new file U U
CMPCOLMO Compare columns: old file U U
CMPLINE Compare lines U U U
CMPSECT Compare sections U U
1
COLHEAD Define column headings U
DPLINE Do not process lines (containing a string) U U U
DPLINEC Do not process lines—continuation U U U
LNCT Line count U U U U U
LPSFV List previous -search -following value U
LSTCOLM List columns U U
NCHGT Change text: new or search file U U U
2
NEXCLUDE Exclude data: new file U U
2
NFOCUS Focus on data: new file U U
NTITLE Alternative listing title: new file U U U U U
NY2AGE Year 2000 aging option: new file U
NY2C Year 2000 date definition: new file, character U
format
NY2Z Year 2000 date definition: new file, zoned U
decimal format
NY2D Year 2000 date definition: new file, unsigned U
packed decimal format
NY2P Year 2000 date definition: new file, packed U
decimal format
OCHGT Change text: old file U U
2
OEXCLUDE Exclude data: old file U U
2
OFOCUS Focus on data: old file U U
Table 27. Summary of Process Statements for Compare and Search (continued)
Valid For
Process Statement Compare Type
Keyword Description FILE LINE WORD BYTE Search
OTITLE Alternative listing title: old file U U U U
OY2AGE Year 2000 aging option: old file U
OY2C Year 2000 date definition: old file, character U
format
OY2Z Year 2000 date definition: old file, zoned U
decimal format
OY2D Year 2000 date definition: old file, unsigned U
packed decimal format
OY2P Year 2000 date definition: old file, packed U
decimal format
REVREF Revision code reference U U
SELECT Select PDS members (MVS) U U U U U
SLIST Statements listing option U U U U U
SRCHFOR Search for a string U
SRCHFORC Search for a string—continuation U
Y2PAST Year 2000 global date option U
* Process Statement comment to be printed U U U U U
.* Process Statement comment not to be U U U U U
printed
Note:
1. Valid only for listing types DELTA and LONG.
2. FILE compare type is valid only with ROWS option of NEXCLUDE, OEXCLUDE, NFOCUS and OFOCUS.
You must include these statements in an input control data set. The process
statements data set can be fixed or variable, and its record length can be large, but
you must enter process statements only in columns 1 through 72. Only one process
statement can be entered per line. SuperC checks process statements and required
operands for completeness before beginning a comparison. Comments are not
allowed at the end of the line after the statement has been completed. Comment
lines should be separate statements. Some statements cause an error message if
comments are included on the same line.
You can enter some process statements several times in the statements data set
(DPLINE or CMPLINE) as they define independent actions to be taken in the
comparison. Others redefine their process scope after their first inclusion (LNCT).
Including more than one redefining statement is not recommended but is not
reported as an error. There is also no specific rule concerning which statement
definition (or re-definition) prevails—the first (least often) or last (most often).
Note: It is best to retain and inactivate old process statements rather than deleting
them from the statement data set. This can be easily done by putting a
period and an asterisk (.*) in the first two character positions. These
statements are ignored and not listed by the SuperC program when the data
set is used as a statement data set.
The SuperC Compare Process Statements are listed alphabetically and defined in
the following sections.
Examples
CHNGV 5 SuperC includes up to 5 match lines before
and after a changed line in the output listing.
Syntax
CHNGV num
Operand Description
num A decimal number between 1 and 1000.
Examples
CMPBOFS NTOP 1000 OTOP 5E00 SuperC interprets the two CMPBOFS
statement sequences as compare from hex
offset 1000 to the last byte of the new data
set and from hex offset 5E00 to the last byte
of the old data set.
CMPBOFS NTOP 1000 CMPBOFS OTOP 5E00 Performs the same function as the statement
in the previous example but it is specified as
two separate statements.
Syntax
CMPBOFS KYWD hex-offset [ ...]
Operand Description
KYWD
The keyword may be one of the following:
TOP New Top and Old Top specification. Defines the byte offset (zero
based) to start the Byte compare for both data sets or members.
BTM New Bottom and Old Bottom specification. Defines the byte offset
(zero based) to end the Byte compare for both data sets or
members. This value may be greater than the data set size but the
omission of the BTM specification accomplishes the same objective.
NTOP New Top. Defines the byte offset (zero based) to start the Byte
compare for the new data set or member.
OTOP Old Top. Same as NTOP but refers to the old data set or member.
NBTM
New Bottom. Defines the last byte position to end the Byte
compare in the new data set or members.
OBTM
Old Bottom. Same as NBTM but refers to the old data set or
member.
Hex offset
A hexadecimal value without quotes. Maximum size: 8 hexadecimal digits.
Note: If you do not specify “TOP”, “NTOP”, or “OTOP”, SuperC defaults to the
top of the data set. If you do not specify “BTM”, “NBTM”, or “OBTM”,
SuperC defaults to the last byte of the data set.
SuperC compares the data from the columns of the input data set. Up to 15
compare ranges/individual-columns are allowed and may be entered on additional
CMPCOLM, CMPCOLMN, or CMPCOLMO statements. The column values and
ranges must be in ascending order.
Notes:
1. Some process options (SEQ, NOSEQ, and COBOL) also define CMPCOLMS.
The CMPCOLMS statement overrides all of these options.
2. CMPCOLM, CMPCOLMN and CMPCOLMO cannot be used for WORD
compare type or Search if the input contains a mixture of DBCS and non-DBCS
data.
3. CMPCOLM, CMPCOLMN and CMPCOLMO cannot be used when using
FOCUS COLS or EXCLUDE COLS.
4. Do not use the CMPCOLM, CMPCOLMN and CMPCOLMO process statements
if the Y2DTONLY process option has been specified.
Compare Types — Line and Word
Examples
CMPCOLM 25:75 Compares columns 25 through 75 in both
data sets.
CMPCOLM 30:60,75 Compares columns 30 through 60 and
column 75 in both data sets.
CMPCOLM 30:60 75 Performs the same function as the previous
example. Notice that the comma and space
are equivalent.
CMPCOLMN 1:72 CMPCOLMO 9:80 Compare different columns from each data
set.
Syntax
CMPCOLM start-colm[:stop-colm][,...]
CMPCOLMN start-colm[:stop-colm][,...]
CMPCOLMO start-colm[:stop-colm][,...]
Operand Description
start-colm A number that identifies the column in which SuperC begins the
comparison.
stop-colm A number that identifies the column in which SuperC ends the
comparison. This number is separated from the start-colm value by
a colon (:).
Examples
CMPLINE TOP 55 BTM 99 Compares lines 55 through 99 in both data
sets.
CMPLINE NTOP 55 NBTM 99 Limits the comparison to lines 55 through 99
in the new data set.
CMPLINE NTOP ’ABCD’,5:66 Starts the comparison when the first ″ABCD″
is detected in columns 5 through 69.
CMPLINE OTOP ’ABCD’ Starts the comparison when SuperC detects
the first “ABCD” in any column of the old
data set.
Syntax
CMPLINE KYWD {rel-line-# }[ ...]
{,’string’[,start-colm[:stop-colm]]}
Operand Description
KYWD
The keyword may be one of the following:
TOP New and Old Top. Defines the beginning line in both data sets or
members.
BTM New and Old Bottom. Defines the ending line in both data sets or
members.
NTOP New Top. Defines the beginning line in the new data set.
NBTM
New Bottom. Defines the ending line in the new data set.
OTOP Old Top. Defines the beginning line in the old data set.
OBTM
Old Bottom. Defines the ending line in the old data set.
rel-line-#
The relative number of the record in the data set or member. Valid range =
1 to 999999.
string Character string enclosed within single quotes. For embedded single
quotes, use two consecutive quotes (''). For example, enter 'don''t' for the
string “don’t”.
start-colm
A number that identifies the column in which SuperC begins its search for
string. All columns to the left of this column are ignored.
stop-colm
A number that identifies the column in which SuperC ends its search for
string, but only for that record. If the data set contains more records, the
search continues with the next record, beginning with the column specified
as the start-colm.
This number is separated from the start-colm value by a colon (:). All
columns to the right of this column are ignored. If the colon and stop-colm
are not entered, only the start-colm value is used. For example, if you
specify ’ABCD’ as a string that must exist between columns 5 and 69, the
search really includes columns 5 to 72. Therefore, the string can be found
even if the first character is in column 69, with the others in columns 70,
71, and 72.
Notes:
1. If SuperC does not find the “top” condition you specify (for example, a pattern
is incorrect), the compare continues but usually reports zero lines processed for
this data set.
2. If you do not specify “TOP”, “NTOP”, or “OTOP”, SuperC defaults to the top
of the data set. If you do not specify “BTM”, “NBTM”, or “OBTM”, SuperC
defaults to the end of the data set.
Examples
CMPSECT SECT01 TOP 25 BTM 50 Compares lines 25 through 50 in both data
sets or members.
CMPSECT SECT02 NTOP 60 NBTM 70 CMPSECT Compares lines 60 through 70 in the new
SECT02 OTOP 65 OBTM 75 data set to lines 65 through 75 in the old data
set.
CMPSECT SECTX TOP ’PART1:’,2:10 CMPSECT Starts the comparison of both data sets when
SECTX BTM ’END PART1:’,2:10 SuperC detects the string “PART1:” in
columns 2 through 10 and ends the
comparison when SuperC detects the string
“END PART1:” in columns 2 through 10.
CMPSECT SECTY NTOP ’PART2:’,2:10 CMPSECT Compares a section in the new data set to a
SECTY OTOP ’PART2:’,6:20 CMPSECT SECTY section in the old data set. The section in the
BTM ’END PART2:’,2:10 new data set begins with the string “PART2:”
in columns 2 through 10 and ends with the
string “END PART2:” in columns 2 through
10. The section in the old data set begins
with the string “PART2:” in columns 6
through 20 and ends with the string “END
PART2:” in columns 2 through 10.
Syntax
CMPSECT KYWD {section-id }[... ]
{,’string’[,start-colm[:stop-colm]]}[...]
Operand Description
KYWD
The keyword may be one of the following:
TOP New and Old Top. Defines the beginning line in both compare
sections.
BTM New and Old Bottom. Defines the ending line in both compare
sections.
NTOP New Top. Defines the beginning line in the new compare section.
NBTM
New Bottom. Defines the ending line in the new compare section.
OTOP Old Top. Defines the beginning line in the old compare section.
OBTM
Old Bottom. Defines the ending line in the old compare section.
section-id
The relative number of the record in the data set or member. Valid range =
1 to 999999.
string Character string enclosed within single quotes. For embedded single
quotes, use two consecutive quotes (''). For example, enter 'don''t' for the
string “don’t”.
start-colm
A number that identifies the column in which SuperC begins its search for
string. All columns to the left of this column are ignored.
stop-colm
A number that identifies the column in which SuperC ends its search for
string, but only for that record. If the data set contains more records, the
search continues with the next record, beginning with the column specified
as the start-colm.
This number is separated from the start-colm value by a colon (:). All
columns to the right of this column are ignored. If the colon and stop-colm
are not entered, only the start-colm value is used. For example, if you
specify ’ABCD’ as a string that must exist between columns 5 and 69, the
search really includes columns 5 to 72. Therefore, the string can be found
even if the first character is in column 69, with the others in columns 70,
71, and 72.
Note: If a “top” condition is not found (for example, a pattern is incorrect), the
compare continues but will usually report zero lines processed for this data
set.
Compare Types
LINE only.
Syntax
COLHEAD heading1, heading2, start-print-column:end-print-column,
N start-column:end-column data-format-indicator,
O start-column:end-column data-format-indicator
Operand Description
heading1 The heading to appear on the first line for the print
column.
heading2 The heading to appear on the second line for the
print column.
start-print-column The starting print column for the heading
specified.
end-print-column The ending print column for the heading specified.
(Must be separated from the start-print-column by a
colon.)
Data Format Indicator The format of the data in the old data set to be
displayed (as for the new data set).
Examples
COLHEAD ’START’,’DATE’,1:7,N 1:6 P,O 11:16 Defines a print column with a heading of
“START” in the first line and “DATE” in
the second heading line, headings to start
in print column 1. The data to be
displayed from the new data set is in
positions 1 through 6 and is in packed
format. The data to be displayed from the
old data set is in positions 11 through 16
and is in (the default) character format.
The Don’t Process Line statement removes from the compare set lines that can be
recognized by either a unique character string or a combination of related strings.
DPLINEC is the continuation of the immediately preceding DPLINE or DPLINEC
process statement. All the strings in a DPLINE/DPLINEC sequence must be found
on the same input line for the line to be excluded.
A start-column or range can also be used to restrict the columns scanned. Relative
start-columns and relative stop-columns are valid only on DPLINEC statements.
This allows you to specify a relative start position depending on the end of the
previous DPLINE/DPLINEC in the sequence relationship. Normal scanning starts
at the beginning of the input line (resulting in the first found string) unless
restricted by user column specifications or the relative operator.
Notes:
1. DPLINE and DPLINEC columns are not restricted by compare columns. The
data patterns are also not affected by the ANYC process option. See Figure 227
on page 459 for more information.
2. The relative start operator “+” introduces another important capability of
backtrack and retry by advancing the starting scan position. Backtrack allows
you to identify a string through a sequence of DPLINE/DPLINEC statements
and have a number of similar strings (all on the same line) be examined until
the correct sequence is found. This contrasts to the “first found”
DPLINE/DPLINEC string and a non-relative DPLINEC rejection when the
DPLINEC condition is not met.
Compare Types — Line and Word
Examples
DPLINE ’ABCDE’ DPLINE ’ABCDE’,1:99999 Each of the following two statements exclude
lines containing the string “ABCDE” from
the compare set.
DPLINE ’AbCde’,2 DPLINE ’AbCde’,2:2 Each of the following two statements exclude
lines where the string “ABCDE” starts in
column 2.
DPLINE ’ABCDE’ DPLINEC ’BDEF ’ Both statements exclude lines that contain
the strings “ABCDE” and “BDEF ”.
DPLINE ’ABCDE’,2:50 Excludes lines where the string “ABCDE”
starts in columns 2 through 50.
DPLINE ’AB’CD’,2:50 Excludes lines where the string “AB'CDE”
starts in columns 2 through 50.
DPLINE X’C1C27BF1’,2:50 Excludes lines where the string “AB,1” starts
in columns 2 through 50.
DPLINE ’ABC’ DPLINEC ’BDEF’,+ Exclude lines containing the string “ABC”
followed in the same line by the string
“BDEF”.
DPLINE ’ABC’s DPLINEC ’BDEF’,+5 Exclude lines containing the string “ABC”
and “BDEF” when the string “BDEF” starts
in the same line 5 columns after the end of
the string “ABC”.
Syntax
DPLINE ’string’[,start-colm[:stop-colm]]
DPLINEC ’string’[,start-colm[:stop-colm]]
[,+start-colm[:+stop-colm]]
[,+]
Operand Description
string Character string enclosed within single quotes. For embedded
single quotes, use two consecutive quotes ('').
start-colm A number that identifies the column in which SuperC begins its
search for string. All columns to the left of this column are ignored.
stop-colm A number that identifies the column in which SuperC ends its
search for string, but only for that record. If the data set contains
more records, the search continues with the next record, beginning
with the column specified as the start-colm.
This number is separated from the start-colm value by a colon (:).
All columns to the right of this column are ignored. If the colon
and stop-colm are not entered, only the start-colm value is used.
This causes a search of a single column for the first character of
string.
All columns to the right of the column that the last character of
string can occupy are ignored. For example, if you specify ’ABCD’
as a string that must exist between columns 5 and 69, the search
really includes columns 5 to 72. Therefore, the string can be found
even if the first character is in column 69, with the others in
columns 70, 71, and 72.
+start-colm The relative column following the end of the previous “Don’t
process” string in which this string must start.
+stop-colm The relative column following the end of the previous “Don’t
process” string in which SuperC ends the search for string.
+ Following the previous “Don’t process” string, scan to the end of
the line for string (same as + 1:99999).
Examples
LNCT 66 Lists up to 66 lines per page.
Syntax
LNCT num
Operand Description
num A decimal number between 15 and 999999.
LSTCOLM column selections must be contiguous and can be no wider than the
output listing line without truncation.
Compare Types — Line only
Examples
LSTCOLM 20:90 Lists columns 20 through 90 in the output
listing.
Syntax
LSTCOLM range
Operand Description
range Two column numbers separated by a single colon (:). Do not leave blanks
on either side of the colon.
Change the input source image before performing the comparison. More than one
change text statement can be contained in the statements data set.
The find-mask and replacement string need not be the same length. The
replacement string may even indicate a null string. Unequal replacements result in
either blank insertions on short replacements (at the end of the found word) or
downstream blank deletions to accommodate larger replacements (deleted blanks
are selected from downstream blank pairs). The net effect of a longer string
replacement of a shorter string shows as a reformat of the original line. The
replaced text line appears in the output instead of the input text.
One or more question marks (“?”) can be used as “wildcard” characters in the
find-mask or string. A wildcard in the output string stores the input character
“as is”.
Compare Types — Line and Word
Examples
NCHGT ’ABCD’,’XXXX’ Changes all “ABCD”s to “XXXX” (exclude)
in the new data set.
OCHGT ’ABCD’,’XXXX’,1:50 Restricts the mask search to columns 1
through 50 in the old data set.
OCHGT ’ABCD’,’,1:50 Changes string “ABCD” to a null string in
columns 1 through 50 in the old data set.
NCHGT X’7B01’,’:1’,6 Uses the hexadecimal string change
convention.
NCHGT ’PREF???’,’NPREF’ Changes the string “PREF” and the wildcard
characters to the string “NPREF”.
NCHGT ’PREF???’,’NPREF??’ Changes the string “PREF” and the first
wildcard character to the string “NPREF”.
The second and third wildcard characters are
not changed.
Syntax
NCHGT ’find-mask’,’string’[,start-colm[:stop-colm]]
OCHGT ’find-mask’,’string’[,start-colm[:stop-colm]]
Operand Description
find-mask The change text string to be replaced. The find-mask must be in
single quotes. Use two consecutive single quotes for quotes within
the find-mask.
string A character string that replaces the contents of find-mask before a
comparison or search. Single quotation marks are required. If the
character string contains a single quotation mark, you must enter it
in the process statement as two single quotation marks.
You can include one or more question marks in the string. It shows
that the position it occupies can be filled by any character, one
character per question mark.
NCHGT ’ ’,’
blank insertion.
NCHGT ’???’,’
Compare Types
FILE (ROWS option only) and LINE.
Syntax
xEXCLUDE KYWD start-position:end-position
where xEXCLUDE can be either NEXCLUDE (new data set) or OEXCLUDE (old
data set), and KYWD can be either ROWS or COLS. COLS is not valid for a FILE
compare.
Operand Description
start-position If ROWS operand used, the first row (record) to be
excluded from the comparison. If COLS operand
used, the first column to be excluded from the
comparison.
end-position If ROWS operand used, the last row (record) to be
excluded from the comparison. If COLS operand
used, the last column to be excluded from the
comparison. (Must be separated from the
start-position by a colon.)
Examples
NEXCLUDE ROWS 5:900 Excludes rows (records) 5 through 900 on the new data set.
OEXCLUDE ROWS 1:900 Excludes rows (records) 1 through 900 on the old data set.
OEXCLUDE COLS 100:199 Excludes columns 100 through 199 on the old data set.
Selects (or “focuses on”) rows or columns of data to be compared. In other words,
only these rows or columns are considered when performing the comparison (or
search) process and all other rows or columns are ignored. Up to 254 “focus”
statements can be entered for each data set.
Notes:
1. NFOCUS and OFOCUS statements are mutually exclusive to NEXCLUDE and
OEXCLUDE statements respectively if using the same operand keyword
(ROWS or COLS).
2. Do not use the NFOCUS or OFOCUS process statement if the Y2DTONLY
process statement has been specified.
3. Valid row range = 1 to 999999.
Compare Types
FILE (ROWS option only) and LINE.
Syntax
xFOCUS KYWD start-position:end-position
where xFOCUS can be either NFOCUS (new data set) or OFOCUS (old data set),
and KYWD can be either ROWS or COLS. COLS is not valid for a FILE compare.
Operand Description
start-position If ROWS operand used, the first row (record) to be
selected for the comparison. If COLS operand used,
the first column to be selected for the comparison.
end-position If ROWS operand used, the last row (record) to be
selected for the comparison. If COLS operand used,
the last column to be selected for the comparison.
(Must be separated from the start-position by a
colon.)
Examples
NFOCUS ROWS 28:90 Selects rows (records) 28 through 90 on the new data set.
OFOCUS ROWS 150:165 Selects rows (records) 150 through 165 on the old data set.
OFOCUS COLS 10:18 Selects columns 10 through 18 on the old data set.
Allows you to specify an alternate data set identification in the output listing
(54-character limit for each title identifier). This replaces the data set and library
names used in the compare.
Note: This option is most useful when a single non-group compare is done on a
temporary data set. The NTITLE/OTITLE identification may be more
meaningful than the actual data set names used in the compare. This is only
allowed for single members or sequential data sets.
Compare Types
File, Line, Word, and Byte
Examples
NTITLE ’New Substitution Name’ Change the titles in the output listing of the
OTITLE ’Old Substitution Name’ new and old data set.
Syntax
NTITLE ’string’
OTITLE ’string’
Operand Description
string The string can be up to 54 characters and must be delimited by single
quotes. Use two consecutive single quotes for each embedded quote. The
string is not checked for valid MVS data set name characters.
Ages all of the defined dates in either the new or old data set. That is, the number
of years specified is added to the “year” portion of each defined date in the data
set concerned.
Note: Dates are defined by the Year 2000 Date Definition process statements NY2C,
NY2Z, NY2D, NY2P, OY2C, OY2Z, OY2D and OY2P; see “NY2C, NY2Z,
NY2D, NY2P, OY2C, OY2Z, OY2D, OY2P —Year 2000 Date Definitions” on
page 430.
Compare Types
LINE
Syntax
NY2AGE years
OY2AGE years
Operand Description
years A number (0 to 999) indicating the number of years by which all defined
dates in the data set are to be aged.
Examples
OY2AGE 28 Ages all defined dates in the “old” data set by 28 years
before being compared. The listing will show the original
date. For example, a defined date in the “old” data set with
a value equating to March 1, 1997, would be aged to March
1, 2025 before being compared to its equivalent in the “new”
data set.
Defines the location and format of a date field on the input data set. Up to 254
date definition statements can be entered for each data set. The matching of the
new to the old dates is performed according to the sequence that the statements
are entered. That is, the first defined old date is matched to the first defined new
date.
If the number of date definition statements for one data set differ to the number of
date definition statements for the other data set, the location and format details for
the “missing” date definition statements are assumed to be the same as their
counterpart date definition statements for the other data set.
Compare Types
LINE
Syntax
xY2y start-column:end-column date-format EMPTY
where xY2y can be either NY2y (new data set) or OY2y (old data set), and y can
be either C (character format), Z (zoned decimal format), D (unsigned packed
decimal format), or P (packed decimal format).
Operand Description
start-column The first position of the date in the input data set.
end-column The last position of the date in the input data set.
(Must be separated from the start-column by a
colon.)
date-format A mask representing the format of the date.
Examples
NY2C 1:8 MMDDYYYY 9:16 MMDDYYYY 21:28 The new data set has dates in character
YYYYMMDD format in columns 1 to 8, 9 to 16 and 21 to
28.
OY2P 5:8 YYMMDD 9:12 YYMMDD The old data set has dates in packed decimal
format in columns 5 to 8 and 9 to 12.
OY2P 101:104 MMDDYY The old data set has a date in packed
decimal format in columns 101 to 104,
NY2Z 101:108 YYYYMMDD The new data set has a date in zoned
decimal format in columns 101 to 108.
NY2C 101:110 YYYY.MM.DD The new data set has a date in character
format (with separators) in columns 101 to
110.
OY2C 93:98 DDMMYY EMPTY The old data set has a date in character
format in columns 93 to 98. If the date field
contains zeros, spaces, low-values, or
high-values, the date in the old data set is
converted before being compared to an
extended format (DDMMYYYY) with a value
of all zeros, spaces, low-values, or
high-values respectively.
Note: BookMaster requires the REFID value to be defined with a :revision tag.
Do not forget the “RUN=YES” attribute if you want your document to have
the change-bar inserted in the processed document.
Compare Types
LINE, WORD
Syntax
REVREF REFID=name
RCVAL=number
Operand Description
REFID=name Name of the revision identifier for the BookMaster :rev/:erev. tags.
RCVAL=number
Numeric revision code for SCRIPT/VS revision tags.
Examples
REVREF REFID=ABC BookMaster example— :rev refid=ABC. and :erev refid=ABC.
tags.
REVREF RCVAL=5 SCRIPT/VS example—.rc 5 on/off delimiters.
For comparisons, the new members are normally compared with old members that
have the same names. Use the colon character (:) to compare members that are not
named alike. SELECT is valid with all compare types.
Compare Types
File, Line, Word, and Byte
Examples
SELECT PROG1,NEWPROG2:OLDPROG2,PROG3 Tells SuperC to make the following
one-to-one comparisons:
NEW MEMBER OLD MEMBER
---------- ----------
PROG1 ⇒ PROG1
NEWPROG2 ⇒ OLDPROG2
PROG3 ⇒ PROG3
Syntax
SELECT new-member[:old-member],...
Operand Description
new-member The name of a new PDS member that is to be compared to an old
PDS member.
old-member The name of an old PDS member that does not have a like-named
member in the new PDS. This member name, if entered, must be
separated from the new-member name by a colon (:).
If the old-member name is not used, SuperC attempts to compare
the new-member to a like-named member of the old PDS.
This statement is useful when there are many process statements and the listing of
these statements in the summary section is not required for problem determination.
For example, a large number of data set selections via SELECT statements would
already be indirectly indicated in the group summary listing section. The SELECT
statement list would then be redundant and generate extra lines in the listing.
Compare Types
File, Line, Word, and Byte
Examples
SLIST OFF Does not list the process statements that
follow this statement.
Syntax
SLIST {ON }
{OFF}
Operand Description
ON Causes the lines in the process statements data set following the SLIST
statement to be listed in the output listing.
OFF Causes the lines in the process statements data set following the SLIST
statement to be suppressed in the output listing.
Note: The Y2PAST process statement should always be used if any of the Year
2000 Date Definition process statements (NY2C, NY2Z, NY2D, NY2P, OY2C,
OY2Z, OY2D, OY2P) have also been used.
Compare Types
LINE
Syntax
Y2PAST fixed
sliding
Operand Description
fixed A 4-digit number indicating a fixed window.
sliding
A 1-digit or 2-digit number indicating a sliding window.
Examples
Y2PAST 1986 A fixed window specifying a 100-year period from 1986 to
2085.
Y2PAST 70 A sliding window specifying (based on the current year
being 1997) a 100-year period from 1927 (70 years in the
past) to 2026.
Y2PAST 5 A sliding window specifying (based on the current year
being 1997) a 100-year period from 1992 (5 years in the past)
to 2091.
Note: Embedding comments as separate lines in the statements data set is a good
programming practice. Period-asterisk comments are useful for inactivating
but retaining old statements in a standard statements data set. These
statements do not get lost, will not appear in the summary section, and can
be reactivated simply by blanking out the period-asterisk characters in
columns 1 and 2.
Examples
* This comment prints in the Search-For listing.
.* This comment does not print in the Search-For listing.
Syntax
{* } comment
{.*}
Operand Description
* Must be in column 1.
.* Must be in columns 1 and 2.
You can enter process options in the Process Options field of the Search-For Utility
panel or select them from one of two Search-For process options panels.
ALLMEMS All members. Search all members including alias entries. This
functions as though all directory entries were selected from a
member list.
ANYC Any case. Lowercase alphabetic characters (a-z) in source data sets
are translated to uppercase (A-Z) before Search-For processing (the
actual input data sets are not modified).
Notes:
1. ANYC has the lowest priority operation affecting the SuperC
process. For example, it does not affect any of the strings used
in SuperC compare process statements (except SRCHFOR).
2. The ANYC process option does not apply to characters in
DBCS text strings.
Use this option to find all strings such as “ABC”, “Abc”, “ABc”.
APNDLST The APNDLST process option appends the listing output to the
specified or default listing data set. If the data set does not exist, it
is allocated as new. Some data sets cannot be appended because of
the append listing attributes and Search-For listing attribute
requirements. There is an error notification for this condition.
Normally, APNDLST allows you to collect listings from separate
searches into one named listing data set (that is, a MOD function).
This objective can sometimes be done without using the APNDLST
option by using multiple SELECT process statements. This allows
you to identify any number of members. It produces a single
composite listing with a single Search-For invocation.
CKPACKL Check for packed format. This option determines if the member or
sequential data set has the standard ISPF packed expansion trigger
format. If required, Search-For unpacks the input data set or
member during the search.
COBOL Ignore columns 1-6 in F 80 data sets. Data in columns 1-6 are
excluded from the search set.
DPACMT Don’t process asterisk (*) comment lines. Lines with an asterisk in
column 1 are excluded from the search set. Other forms of
assembler comments are unaffected. Hence, it is not possible to
have Search-For filter out assembler comments appearing on the
same line as an assembler statement or directive.
DPADCMT Don’t process ADA-type comments. ADA comments are whole or
part lines that appear after the special “--” sequence. Blank lines
are also considered part of the comment set. This option produces
a listing with all comments removed and blanked.
DPBLKCL Don’t process blank lines. Source lines in which all of the search
columns are blank are excluded from the Search-For set. It is
redundant, but not incorrect, to use this option with DPADCMT,
DPPLCMT, and DPPSCMT.
You must include these statements in an input control data set. The process
statements data set can be fixed or variable, and its record length can be large, but
you must enter process statements only in columns 1 through 72. Only one process
statement can be entered per line. Search-For checks process statements and
required operands for completeness before beginning a comparison. Comments are
not allowed at the end of the line after the statement has been completed.
Comment lines must be separate statements.
You can enter process statements in the statements data set more than once (for
example, DPLINE, SELECT, or CMPLINE) as they define independent actions to be
taken. Others redefine their process scope after their first inclusion (for example,
LNCT). Including more than one redefining statement is not recommended but is
not reported as an error. There is also no specific rule concerning which statement
definition (or redefinition) prevails—the first (least often) or last (most often).
Note: It is best to inactivate old process statements that you do not need rather
than deleting them from the statement data set. This can be easily done by
putting a period and an asterisk (.*) in the first 2 character positions. These
statements will be ignored by the Search-For program when the data set is
used as a statement data set.
Examples
CMPCOLM 25:75 Searches columns 25 through 75.
CMPCOLM 30:60,75 Searches columns 30 through 60 and column
75.
CMPCOLM 30:60 75 Performs the same function as the previous
statement.
Syntax
CMPCOLM start-colm[:stop-colm][,...]
Operand Description
start-colm A number that identifies the column in which Search-For begins
the search. All columns to the left of this column are ignored.
stop-colm A number that identifies the column in which Search-For ends its
search. If the data set contains more records, the search continues
with the next record, beginning with the column specified as the
start-colm.
This number is separated from the start-colm value by a colon (:).
All columns to the right of this column are ignored. If the colon
and stop-colm are not entered, only the start-colm value is used.
Examples
CMPLINE NTOP 55 NBTM 99 Search new data set between lines 55
through 99.
CMPLINE NTOP ’ABCD’,5:66 Start new data set search when SuperC
detects the first “ABCD” in columns 5
through 69.
CMPLINE NBTM ’ABCD’ End new data set search on first “ABCD”
found in any column.
Syntax
CMPLINE KYWD {rel-line-# }[ ...]
{,’string’[,start-colm[:stop-colm]]}
Operand Description
KYWD The keyword may be one of the following:
NTOP New Top. Defines the beginning line in the new (search)
data set.
NBTM
New Bottom. Defines the ending line in the new (search)
data set.
rel-line-# The relative number of the record in the data set or member. Valid
range = 1 to 999999.
string Character string enclosed within single quotes. For embedded
single quotes, use two consecutive quotes (''). For example, enter
’don’t’ for the string “don’t”.
start-colm A number that identifies the column in which Search-For begins
looking for string. All columns to the left of this column are
ignored.
stop-colm A number that identifies the column in which Search-For ends its
search for string, but only for that record. If the data set contains
more records, the search continues with the next record, beginning
with the column specified as the start-colm.
This number is separated from the start-colm value by a colon (:).
All columns to the right of this column are ignored. If the colon
and stop-colm are not entered, only the start-colm value is used.
This causes a search of a single column for the first character of
string.
All columns to the right of the column that the last character of
string can occupy are ignored. For example, if you specify ’ABCD’
as a string that must exist between columns 5 and 69, the search
really includes columns 5 to 72. Therefore, the string can be found
even if the first character is in column 69, with the others in
columns 70, 71, and 72.
Removes from the search set a line that can be recognized by either a unique
character string or combination of related strings all appearing on the same input
line. DPLINEC is the continuation of the immediately preceding DPLINE or
DPLINEC process statement. All the strings in a DPLINE/DPLINEC sequence
must be found on the same input line for the line to be excluded.
Examples
DPLINE ’ABCDE’ DPLINE ’ABCDE’,1:99999 Both statements exclude lines containing the
string “ABCDE” from the compare set.
DPLINE ’AbCde’,2 DPLINE ’AbCde’,2:2 Both statements exclude lines where the
string “ABCDE” starts in column 2.
DPLINE ’ABCDE’ DPLINEC ’BDEF ’ Exclude lines that contain the strings
“ABCDE” and “BDEF ”.
DPLINE ’ABCDE’,2:50 Excludes lines where the string “ABCDE”
starts in columns 2 through 50.
DPLINE ’AB’CD’,2:50 Excludes lines where the string “AB'CDE”
starts in columns 2 through 50.
DPLINE X’C1C27BF1’,2:50 Excludes lines where the string “AB,1” starts
in columns 2 through 50.
DPLINE ’ABC’ DPLINEC ’BDEF’,+ Exclude lines containing the string “ABC”
followed in the same line by the string
“BDEF”.
DPLINE ’ABC’s DPLINEC ’BDEF’,+5 Exclude lines containing the string “ABC”
. and “BDEF” when the string “BDEF” starts
in the same line 5 column positions after the
end of the string “ABC”.
Syntax
DPLINE ’string’[,start-colm[:stop-colm]]
DPLINEC ’string’[,start-colm[:stop-colm]]
[,+start-colm[:+stop-colm]]
[,+]
Operand Description
string Character string enclosed within single quotes. For embedded
single quotes, use two consecutive quotes (’’).
start-colm A number that identifies the column in which Search-For begins
looking for string. All columns to the left of this column are
ignored.
stop-colm A number that identifies the column in which Search-For ends its
search for string, but only for that record. If the data set contains
more records, the search continues with the next record, beginning
with the column specified as the start-colm.
Examples
LNCT 66 Lists up to 66 lines per page.
Syntax
LNCT num
Operand Description
num A decimal number between 15–999 999.
Examples
LPSFV 2 Lists up to 2 lines before and after the line
where Search-For finds the search string.
Syntax
LPSFV num
Operand Description
num A decimal number between 1 and 50.
LSTCOLM column selections must be contiguous and can be no wider than the
output listing line without truncation.
Examples
LSTCOLM 20:90 Lists columns 20 through 90 in the output
listing.
Syntax
LSTCOLM range
Operand Description
range Two column numbers separated by a single colon (:). Do not leave blanks
on either side of the colon.
The find-mask and replacement string need not be the same length. The
replacement string may even indicate a null string. Unequal replacements result in
either blank insertions on short replacements (at the end of the found word) or
downstream blank deletions to accommodate larger replacements (deleted blanks
are selected from downstream blank pairs). The net effect of a longer string
replacement of a shorter string shows as a reformat of the original line. The
replaced text line appears in the output instead of the input text.
One or more question marks (“?”) can be used as “wildcard” characters in the
find-mask or string. A wildcard character in the output string stores the input
character as is.
Examples
NCHGT ’ABCD’,’XXXX’ Changes all “ABCD”s to “XXXX”s (exclude)
in the new data set.
NCHGT ’ABCD’,’XXXX’,1:50 Restricts the mask search to columns 1
through 50.
NCHGT ’ABCD’,’,1:50 Changes string “ABCD” to a null string in
columns 1 through 50.
NCHGT X’7B01’,’:1’,6 Uses the hexadecimal string change
convention.
NCHGT ’PREF???’,’NPREF’ Changes the string “PREF” and the wildcard
characters to the string “NPREF”.
NCHGT ’PREF???’,’NPREF??’ Changes the string “PREF” and the first
wildcard character to the string “NPREF”.
The second and third wildcard characters are
not changed.
Syntax
NCHGT ’find-mask’,’string’[,start-colm[:stop-colm]]
Operand Description
find-mask The change text string to be replaced. The find-mask must be in
single quotes. Use two consecutive single quotes for quote
characters within the find-mask.
string A character string that is to replace the contents of find-mask before
a comparison or search. Single quotation marks are required. If the
character string contains a single quotation mark, you must enter it
in the process statement as two single quotation marks.
You can include one or more question marks in the string. It
indicates that the position it occupies can be filled by any
character, one character per question mark.
If there is not enough space for the string to be substituted, the
substitution does not occur. Instead, a warning message is printed
at the bottom of the listing.
start-colm A number that identifies the column in which Search-For begins
looking for string. All columns to the left of this column are
ignored.
stop-colm A number that identifies the column in which Search-For ends its
search for string, but only for that record. If the data set contains
more records, the search continues with the next record, beginning
with the column specified as the start-colm.
This number is separated from the start-colm value by a colon (:).
All columns to the right of this column are ignored. If the colon
and stop-colm are not entered, only the start-colm value is used.
This causes a search of a single column for the first character of
string.
All columns to the right of the column that the last character of
string can occupy are ignored. For example, if you specify ’ABCD’
as a string that must exist between columns 5 and 69, the search
really includes columns 5 to 72. Therefore, the string can be found
even if the first character is in column 69, with the others in
columns 70, 71, and 72.
Notes:
1. Replacing a string with a longer string is not always possible with some lines.
A warning message appears when this happens and the problem change-text
statement is designated in the summary section.
2. A string replacement using the “null” character notation does not always work
as first envisioned. Nulling a character string only shifts following characters
up through the next blank character. One or more blank pad characters are
applied to take up the null positions of the original string. Only nonblank
character strings are shifted, not entire lines.
NCHGT ’ ’,’
blank insertion.
NCHGT ’???’,’
Allows you to specify an alternate data set identification in the output listing
(54-character limit for each title identifier). This replaces the data set and library
names used in the search.
Note: This option is most useful when a single non-group search is done on a
temporary data set. The NTITLE identification may be more meaningful
than the actual data set names used in the search.
Examples
NTITLE ’New Substitution Name’ Change the titles in the output listing of the
data set.
Syntax
NTITLE ’string’
Operand Description
string The string can be up to 54 characters and must be delimited by single
quotes. Use two consecutive single quotes for each embedded quote. The
string is not checked for valid MVS data set name characters.
Examples
SELECT PROG1,NEWPROG2,PROG3 Selects PDS members PROG1, NEWPROG2,
and PROG3 to be searched.
Syntax
SELECT new-member[...]
Operand Description
new-member The name of the PDS member that is to be searched.
This statement is useful when there are many process statements and the listing of
these statements in the summary section is not required for problem determination.
Examples
SLIST OFF Does not list the process statements that
follow this statement.
Syntax
SLIST {ON }
{OFF}
Operand Description
ON Causes the lines in the process statements data set following the SLIST
statement to be listed in the output listing.
OFF Causes the lines in the process statements data set following the SLIST
statement to be suppressed in the output listing.
Specifies the string and the string type (P - prefix, W - word, S - suffix, or blank -
for any occurrence of the string). SRCHFORC is the continuation of the
immediately preceding SRCHFOR or SRCHFORC process statement. All the strings
in a SRCHFOR/SRCHFORC group must be found on the same input line.
Examples
SRCHFOR ’ABC’ Searches for string “ABC” within search
columns.
SRCHFOR ’ABC’,W Searches for “ABC” as word string.
SRCHFOR X’4004’ Searches for hex string within search
columns.
SRCHFOR ’A’bc’ Searches for string “A'bc”.
SRCHFOR ’ABC’,5:10 “ABC” starts within 5:12 of search columns.
SRCHFOR ’ABC’,W,5 Word “ABC” starts in column 5.
SRCHFOR ’ABC’ SRCHFORC ’DEF’ Finds “ABC” and “DEF” on same line within
the search columns.
SRCHFOR ’ABC’ SRCHFORC ’DEF’,+ Finds “DEF” to the right of first “ABC”
string.
SRCHFOR ’ABC’ SRCHFORC ’DEF’,+1:9999 Same as above example.
SRCHFOR ’ABC’ SRCHFORC ’DEF’,W,+ Same as above, but “DEF” must be a word.
SRCHFOR ’ABC’ SRCHFORC ’DEF’,+5 Same as above, but “DEF” must start in fifth
column after “ABC”.
SRCHFOR ’ABC’ SRCHFORC ’DEF’,+5 SRCHFORC Same as above, but “GKL” must also be
’GKL’ found on the same line.
Syntax
SRCHFOR ’string’[,P][,start-colm[:stop-colm]]
[,S]
[,W]
SRCHFORC ’string’[,P][,start-colm[:stop-colm]]
[,S][,+start-colm[:+stop-colm]]
[,W][,+]
Operand Description
string Character string enclosed within single quotes. For embedded
single quotes, use two consecutive single quotes ('').
P Prefix. String begins a word, but is not the complete word
(Example: string “abc” is a prefix to the word “abcdef”).
S Suffix. String ends a word, but is not the complete word (Example:
string “def” is a suffix to the word “abcdef”).
W Word. String is a complete word. Words are delimited by blanks, or
end-of-line characters.
start-colm A number that identifies the column in which Search-For begins
looking for string. All columns to the left of this column are
ignored.
stop-colm A number that identifies the column in which Search-For ends its
search for string, but only for that record. If the data set contains
more records, the search continues with the next record, beginning
with the column specified as the start-colm.
This number is separated from the start-colm value by a colon (:).
All columns to the right of this column are ignored. If the colon
and stop-colm are not entered, only the start-colm value is used.
This causes a search of a single column for the first character of
string.
All columns to the right of the column that the last character of
string can occupy are ignored. For example, if you specify ’ABCD’
as a string that must exist between columns 5 and 69, the search
really includes columns 5 to 72. Therefore, the string can be found
even if the first character is in column 69, with the others in
columns 70, 71, and 72.
+start-colm The relative column (starting from the column where the string of
SRCHFOR/SRCHFORC ended) in which the string must start for
the multiple statement relation to be met. Only SRCHFORC
statements can contain relative start-columns.
+stop-colm The number that identifies the relative column (starting from the
column where the string of the last SRCHFOR/SRCHFORC ended)
in which Search-For ends its search for string. Only SRCHFORC
statements can contain a relative stop-colm.
+ Continues the scan after the pattern to the end of the line (same as
+1:99999).
Note: Embedding comments as separate lines in the statements data set is a good
programming practice. Period-asterisk comments are useful for inactivating
but retaining old statements in a standard statements data set. These
statements do not get lost, will not appear in the summary section, and can
be reactivated simply by blanking out the period-asterisk characters in
columns 1 and 2.
Examples
* This comment prints in the Search-For listing.
.* This comment does not print in the Search-For listing.
Syntax
{* } comment
{.*}
Operand Description
* Must be in column 1.
.* Must be in columns 1 and 2.
Return Codes
Results from calling the SuperC program are returned as condition codes from
SuperC. The SuperC and SuperCE utilities generate a short message and a long
message to interpret the results for you. However, only the long message displays
the return codes, which are:
0 Normal completion. No differences were found in the input data sets.
1 Normal completion. Differences were found in the input data sets.
4 Warning. Erroneous or conflicting input options were detected by the
SuperC program. Data sets were compared, but should be checked for
results consistent with those expected. Check listing for more details.
6 Warning. The old data set did not contain proper sequence numbers, or the
sequence number intervals were not large enough to contain insert activity.
This return code applies only to results from the UPDCMS8, UPDMVS8,
and UPDSEQ0 process options.
8 Error. Error on old input data set. The data sets were not compared. Check
output for more information.
12 Error. Inconsistent data set organizations. The new and old data sets are
not both PDSs or sequential data sets. The compare was not run.
16 Error. Error on new input data set. The data sets were not compared.
Check output for more information.
20 Warning. Error on update data set; one of the following:
v Missing DELDD
v I/O error
v Append to PDS
v Incorrect attributes on an append or PDS output operation.
Processing was completed with the update options reset and ignored. The
error can also be returned if an update data set is being used
simultaneously as the listing data set.
24 Error. Error occurred during open or during writing to the listing data set.
The error can also be returned because of a new or old input data set
simultaneously being used as the listing data set. No additional
information is generated to better define the error condition.
25 Error. The listing data set was not allocated because of a conflict with the
logical record length (LRECL), record format (RECFM), or data set
organization. A listing can be saved only in a PDS that has the same
LRECL or RECFM; a listing can never be appended to a PDS by using the
APNDLST process option; a listing can be appended by using the
APNDLST process option only to a sequential data set that has the same
LRECL or RECFM. No output was generated.
SCLM Version Compare considerations
This return code is expected if the listing data set is partitioned but the
member name is omitted. Correct the specification and try again.
26 Error. The listing data set could not be extended and is full
(E37 condition). The results are truncated and incomplete.
28 Error. No data was compared because the old and new data sets were
empty. Member names were invalid or there was nothing left to compare
after input filtering. See the listing for more information.
32 Error. Insufficient storage was available for the SuperC program to run.
The user region size was either too small or storage was too fragmented.
SuperC is unique in that, except for files that are identical, it does not determine
matching sections until it has completely read both files. Missing data units are
units that are out of sequence, as opposed to units that have been deleted from a
file. During a comparison, SuperC finds all matches, locates the largest set of
matching data units, and recursively allows this compare set to divide the file into
additional partitioned subsections. All new subsections are processed for
corresponding matches. The subprocess ends when no more matches can be found
within corresponding new and old file partitioned subsections. Sections classified as
inserted or deleted are corresponding areas for which SuperC could not find a
match.
Figure 228 shows an example of a comparison of two files that are identified as
having lines represented by A, B, C, ... F. The SuperC algorithm attempts to find
the best match set from the input lines. Notice how the match set requires
consideration of duplicate lines.
An equally important SuperC concern would be whether it finds the best match set
and whether it finds all matches. Unfortunately, the match-finding algorithm is not
perfect. Ignoring the false match masking problem, and the large number of
duplicate source lines obscuring the match set possibilities, occasional matches can
be overlooked.
A fixed partitioning size of 32K lines/words/bytes was selected that was based on
some test studies. The compare processes up to this limit and iteratively adjusts the
intermediate ending break point of the pass by an adaptive method. Continuation
from the adjusted end point is the basis for the next pass. That end point might
even be adjusted to some previous records that had already been processed. The
objective is to achieve the next best compare set for future unprocessed records.
The overall process ends when both files reach the End-of-File during a pass. The
results from the intermediate passes are combined into one user end result. Most
large compares are never suspected to have been partitioned and recombined.
The unlimited file size solution may appear, at first, unnecessary for Line compare
using a virtual address space that is nearly unlimited. Yet there often has to be
some limit—even if it is a high value. Programs need to store data with
predetermined precision limits and programs work better with limits that are
reasonable. Word compare and Byte compare eventually needed a partitioning
limit for the compare as the number of words and bytes become large even for
small file sizes.
When you compare or search entire data sets by using an asterisk (*) for a member
name pattern, only real members, not aliases, are processed. For compare, all
directory entries (for both real members and aliases) are analyzed. Messages
appear at the end of the SuperC output listing that give information about
unpaired alias entries for paired real members as follows:
"NEW" PAIRED MEMBERS WITH "NEW" ALIAS MEMBERS NOT PAIRED FOLLOW:
MEMBER1/ALIAS1 MEMBER1/ALIAS2 MEMBER2/ALIAS1 ...
or
"OLD" PAIRED MEMBERS WITH "OLD" ALIAS MEMBERS NOT PAIRED FOLLOW:
MEMBER1/ALIAS1 MEMBER1/ALIAS2 MEMBER2/ALIAS1 ...
The complex data format on DASD is dependent on the load module data set
block size, and defined storage definitions which are controlled by the linkage
editor. The size stored by the linkage editor in the PDS directory may differ from
the DASD data byte count reported by SuperC and Browse depending on the
characteristics of the load module.
If load modules are exact copies of each other, SuperC should find no differences.
If load modules have been link-edited from the same object but with different
block sizes, SuperC will probably report they are different.
Because of the relative DASD addresses (TTRs) in load modules, the recommended
procedure for comparing load modules which have not been reblocked is to use
the AMBLIST utility with LISTLOAD OUTPUT=MODLIST against both load
modules, then use SuperC to compare the two AMBLIST outputs. There is no easy
way to compare load modules with different internal record sizes such as occurs
when COPYMOD or LINKEDIT processes them.
Comparing CSECTs
SuperC compare of PDS Load Module Csects (using the LMCSFC Process Option)
can return unexpected differences. SuperC looks at the length of the Csect from the
control record immediately preceding the Csect data record in the load module.
This physical data length can differ from the logical Csect data length in the load
module header that the AMBLIST utility uses to report the length of the Csect.
SuperC always compares all of the physical data in each Csect. You can use
SuperC Byte compare to examine the Csect data content in detail.
methods are not warranted by the ISPF product, a sample CLIST and a sample
PROCLIB procedure are distributed as an aid in the SAMPLIB data set as members
ISRSCLST and ISRSPROC.
The sample CLIST allows a TSO user to enter a line command to communicate the
operational parameters directly to the SuperC program without displaying the ISPF
panels. The sample CLIST will request entry of a search pattern or string. A sample
SuperC call as entered on the terminal might look like:
superc newfile(.newdata.file) oldfile(ludlow.olddata.file)
or
exec clist(superc) ’new(.newdata.file) old(ludlow.olddata.file)’
where superc is the command and newfile and oldfile are the keywords for the input
files.
Examples
The following example shows a SuperC compare JCL sequence:
The sequence allows the SuperC program to compare two input data sets and
generates a line compare CHANGE type listing to the spool output queue and a
separate UPDCNTL update control data set output using source columns 2
through 72.
A catalog procedure is a set of “canned” JCL statements that you can invoke as an
extension of your own JCL. A simplified JCL sequence appears below:
//SUPERC JOB
// EXEC SUPERC,
// NEWFILE=’DLUDLOW.GROUP.DATA1’,
// OLDFILE=’MFRAME.GROUP.DATA2’,
// LISTING=DELTA
// JOB
//SEARCH EXEC PGM=ISRSUPC,PARM=(’SRCHCMP,ANYC’)
//STEPLIB DD DSN=ISPF330.LOAD,DISP=SHR
//NEWDD DD DSN=USERID.PDS,DISP=SHR
// DD DSN=USERID.PDS2,DISP=SHR
//OUTDD DD SYSOUT=*
//SYSIN DD *
SRCHFOR ’NEEDLE’,W,10:20
/*
//
Note: Listing types are not applicable for the File compare type. For information
about File compare listings, see “Effect of File Compare Type on SuperC
Listings” on page 477.
OVSUM Lists only an overall summary of the results of the comparison
without showing the differences themselves.
For example, an OVSUM listing of a Line comparison shows how
many lines matched, how many were reformatted, how many were
inserted, and so forth.
DELTA Lists only the differences between the source data sets or members
being compared, followed by overall summary results. Differences
are flagged to the left of each output line.
For example, a DELTA listing of a Line comparison shows only the
individual lines in each data set or member that are different.
CHNG Same as the DELTA listing, plus up to 10 matching lines, words, or
bytes before and after the differences. This shows the differences
within the context of the surrounding lines.
For example, suppose a comparison of two data sets shows that
each has 15 lines that match, followed by one or more lines that
are different, followed by 15 more lines that match. A CHNG
listing of a Line comparison of these data sets would show the
lines in each data set or member that are different, plus 10 of the
15 lines that match, both before and after.
LONG Same as the CHNG listing, except this listing shows the entire new
data set, plus any data from the old, or original, data setthat is not
in the new, or changed, data set.
If we borrow the example used in the CHNG listing definition, a
LONG listing would include all 15 matching lines, not just 10.
The following sections begin by explaining the information displayed in the titles
lines and at the bottom of the listings. Then, each listing type is discussed in more
detail, with examples of listings and descriptions of the listing sections.
DATA, as the only member name common to both data sets, is the only member
compared. Figure 229 on page 468 shows the source data for both the old and new
versions of DATA. Figure 230 on page 468 shows the results of an OVSUM
comparison of the two versions.
Figure 229. Split Screen Showing Source Data for SuperC Listings
Figure 233 shows how COLHEAD process statements have been used to generate
column headings (Account Number, Birth Date, and Surname) for the corresponding
input data. For more information, see “COLHEAD—Define Column Headings” on
page 418.
The second title line shows you the names of the new and old data sets that were
compared when the listing was created.
Type-of-Difference Codes
At the far right of some listings are headings that provide additional information
about the types of differences SuperC has found. Headings you may see are:
TYPE An abbreviation that identifies the type of difference:
MAT= Matched lines.
RFM= Reformatted lines.
RPL= Replaced lines.
INS= Lines that are in the new data set, but not in the old data set.
DEL= Lines that are in the old data set, but not in the new data set.
IMR= Lines in the new data set that have been moved from where they
were in the old data set and reformatted. Listing should show a
matching DMR= flag for a line in the old data set.
DMR=
Lines in the old data set that have been moved and reformatted in
the new data set. Listing should show a matching IMR= flag for a
line in the new data set.
IMV= Lines in the new data set that have been moved from where they
were in the old data set. Listing should show a matching DMV=
flag for a line in the old data set.
DMV=
Lines in the old data set that have been moved in the new data set.
Listing should show a matching IMV= flag for a line in the new
data set.
LEN The number of consecutive lines flagged by one of the TYPE abbreviations.
N-LN# and O-LN#
The line number(s) where the flagged line appears in either or both data
sets. For insertions, the O-LN# column shows where the line would have
appeared in the old data set. For deletions, the N-LN# column shows
where the line would have appeared in the new data set.
Figure 234. Word Comparison of Two PDSs Using Change Bar to Show Differences (Part 1 of 2)
Figure 234. Word Comparison of Two PDSs Using Change Bar to Show Differences (Part 2 of 2)
This part also shows how many members were processed, had changes, had no
changes, and were not paired, with the last category provided for both new and
old members.
As the sample listing shows, one member was processed and had changes. It also
shows that both PDSs contain two non-paired members. The non-paired heading
means that these members were not included in the comparison because they were
not paired with members in the other PDS. The names of these members are
shown in the second part of the Member Summary Listing, PAGE 3 of Figure 234
on page 473.
However, for comparisons of complete PDSs, as PAGE 4 of Figure 234 on page 473
shows, the summary is called:
PDS XXXX OVERALL TOTALS
In both headings, the XXXX is replaced by the compare type being used, such as
WORD. As the sample listing shows, the left side of a LONG listing of a Word
comparison shows how many words were matched, inserted, deleted, and
processed. Several of these categories are related. For instance, the number of lines
processed in the new data set should be equal to the number of line matches, the
reformatted lines, and the new file line insertions. The number of processed lines
does not include lines that were excluded from processing by a process option or
statement, such as the DPLINE process option.
The left side of the sample listing also shows that the SuperC program corrected a
false match, which it occasionally may detect on the first pass and reclassify as an
insert/delete pair. The new classification is correct, but may have caused the
process to overlook an alternate match. However, this condition should not occur
frequently, which means your comparison results probably will not be affected. The
SuperC program never incorrectly calls a data unit (file, line, word, or byte) a
match when it should be a mismatch.
On the right side, the listing shows the total number of changes, the number of
lines classified as changed/inserted and changed/deleted, and the number of lines
processed. In a Line comparison listing, as shown in Figure 231 on page 469, these
are called paired changes. Paired changes show, for example, that a line inserted in
the new data set corresponds to a line deleted from the old data set. The opposite
would be true for non-paired insertions or deletions.
The number given as total changes should be the sum of the paired changes,
non-paired insertions, and non-paired deletions. For example, in Figure 231 on
page 469, the right-side totals are the equivalent of the following:
2 PAIRED CHANGES
1 NON-PAIRED INSERTS
+ 0 NON-PAIRED DELETES
--
3 TOTAL CHANGES
Bottom-of-Listing Information
The following list describes information that may appear at the bottom of your
SuperC listings. Figure 234 on page 473 shows an example.
v The LISTING-TYPE generated: OVSUM, DELTA, CHNG, or LONG
v The COMPARE-COLUMNS, or the range of columns compared, expressed as
two numbers separated by a colon. For example, 1:76 means SuperC compared
columns 1 to 76 in both data sets. If two column ranges are shown, the first is
the range compared in the new data set or member and the second is the range
compared in the old data set or member.
v The length in bytes of the LONGEST-LINE found in any data set or member
compared
v A list of the PROCESS OPTIONS USED
v A list of the PROCESS STATEMENTS USED
v Warnings and error messages.
Y2K Comparison
Figure 235 shows how the two Year 2000 date definition process statements have
each caused an information (INFO) line to be generated. The information line
shows:
v the position of the defined date in the record
v the contents of the defined date field
v the date as it was actually compared. In the second information line, you can see
the defined date has a 2-digit year portion (″97″) but has actually been compared
using a 4-digit year portion (″1997″).
For more information, see “NY2C, NY2Z, NY2D, NY2P, OY2C, OY2Z, OY2D, OY2P
—Year 2000 Date Definitions” on page 430.
Note: Occasionally, you might see some ″unusual″ characters on the inserted (I)
and deleted (D) lines. These characters simply represent data that is in a
non-character (and therefore not directly printable) format in the input
record. You can ignore them.
Side-By-Side Listings
Two process options, NARROW and WIDE, let you produce listings that show
source data side-by-side (Figure 236 on page 477) instead of interspersed
(Figure 231 on page 469). The NARROW process option shows up to 55 columns
from each member, while the WIDE process option shows up to 80. The listing is
truncated if it exceeds the line length of the process option being used.
Figure 236. Side-By-Side LINE Comparison Using the NARROW Process Option (Part 1 of 2)
Figure 236. Side-By-Side LINE Comparison Using the NARROW Process Option (Part 2 of 2)
The names of the paired and non-paired members are listed at the bottom.
Search-For Listings
You can also produce listings by using the Search-For utility (option 3.14) and the
Extended Search-For utility (option 3.13.S). A sample listing is shown in Figure 239.
This listing was produced by searching all the members of a PDS named
USERID.TEST.SCRIPT and by using the ASIS fields on the Extended Search-For
Utility panel, as follows:
ASIS . . . . ’This line is’
ASIS . . . . ’both members’ c
PAGE 1 of the listing shows that both strings were found in lines 3 and 5 of
member DATA. However, instead of just showing the strings that were being
searched for, the listing shows each line in its entirety.
The APNDUPD process option is available with the Line, Word, and Byte compare
types.
All UPDCMS8 control statements are identified by the characters “./” in columns 1
and 2 of the 80-byte record, followed by one or more blanks and additional
blank-delimited fields. The control statements are sequence (S), insert (I), delete
(D), replace (R), and comment (*).
Data sets created with the UPDCMS8 process option can be used as input to the
CMS UPDATE command, as described in VM/SP CMS Command Reference and
VM/SP CMS Macros and Functions Reference. Figure 240 shows an example of an
UPDCMS8 update data set.
The record attributes for both input data sets must be F 80. They must also contain
sequence numbers.
UPDCNTL—Update Control
This process option produces a control data set that relates matches, insertions,
deletions, and reformats to:
v The relative line numbers of the old and new data sets (Line compare)
v The relative word position of the old data set (Word compare)
v The relative byte offset (Byte compare).
No source or data from either input data set is included. The following panels
show the format used with each of these compare types.
The top of Figure 241 shows the names of the new and old input data sets, along
with the date and time the update data set was created. Table 30 shows the column
numbers used to display the update information:
Table 30. UPDCNTL Format Using Line Compare
Column Numbers Data Item
4–11 New line number
13–20 Old line number
22–29 Match length
31–38 Insert length
40–47 Delete length
49–56 Reformat length
The top of Figure 242 shows the names of the new and old input data sets, along
with the date and time the update data set was created. Table 31 shows the column
numbers used to display the update information:
Table 31. UPDCNTL Format Using Word Compare
Column Numbers Data Item
4–11 Beginning new line number
13–20 Number of lines
22–26 New column number (beginning of word)
28–35 Number of matching words
37–44 Number of new inserted words
46–53 Number of old deleted words
55–62 Beginning old line number
64–71 Number of old lines
73–77 Old column number
The top of the first panel in Figure 243 shows the names of the new and old input
data sets, along with the date and time the update data set was created. The
second panel shows the result of scrolling down to see the remainder of the data
set.
Table 32 on page 485 shows the column numbers used to display the update
information:
The format of the generated data may be suitable as input to the IEBUPDTE utility.
Refer to OS/VS2 MVS Utilities for information about the contents of this data set.
Figure 244 shows an example of an UPDMVS8 update data set.
The data sets to be compared must have a record format of F 80. They must also
contain sequence numbers.
The format of the generated data may be suitable for direct editing. Figure 245 on
page 486 shows an example of an UPDLDEL update data set.
The data set produced is a variable length data set that reflects the input source
data set’s characteristics. Prefix codes, such as I for insert, and the line number
precede lines from the source data sets. Abbreviations show the total number of
consecutive lines flagged as changed, such as INS#= for the number of consecutive
inserted lines. The number of replaced lines (RPL#=) always refers to consecutive
pairs of inserted and deleted lines. Figure 246 on page 487 shows an example of an
UPDPDEL update data set. The first panel shows only the first 80 columns; the
second panel shows the result of scrolling right to see the remainder of the
member.
UPDREV—Update Revision
This process option produces an update file containing a copy of the new source
text with revision tags delimiting the changed text lines.
The UPDREV process option is available for LINE and WORD compare types.
UPDREV supports two different types of revision tags, one for SCRIPT/VS data
sets and one for BookMaster data sets. (Use the REVREF process statement to
specify which type of revision tag you want—see “REVREF—Revision Code
Reference” on page 433).
Figure 247 shows a SuperC UPDREV data set with SCRIPT/VS revision tags (.rc
on/off).
.rc 1 ¦
.rc 1 on
This line is reformatted; the spacing in the "new" file differs.
.rc 1 off
This line is the same in both files.
.rc 1 on
This line differs from the text in the "old" file.
.rc 1 off
This line is the same in both files.
.rc 1 on
This line is in the "new" file, but not in the "old".
.rc 1 off
Note: The revision character (“¦” in the example in Figure 247) can be specified
either by using a REVREF process statement (see “REVREF—Revision Code
Reference” on page 433) or by having a SCRIPT/VS .rc. revision tag as the
first record in the new data set. Subsequent changes to the source can
therefore be separately identified by using different revision characters.
Figure 248 shows a SuperC UPDREV data set with BookMaster revision tags
(:rev/:erev).
:rev refid=ABC.
This line is reformatted; the spacing in the "new" file differs.
:erev.
:rev refid=ABC.
This line is the same in both files.
:erev.
:rev refid=ABC.
This line differs from the text in the "old" file.
:erev.
:rev refid=ABC.
This line is the same in both files.
:erev.
:rev refid=ABC.
This line is in the "new" file, but not in the "old".
:erev.
Figure 248. Example of a UPDREV Update Data Set for BookMaster Documents
When the UPDREV update data set in Figure 248 is subsequently processed by
BookMaster, the final formatted output will have the revision character associated
with the revision ID abc (as specified by a :revision. &bookie tag in the new
input data set) in the left margin of the output document identifying the changed
lines (those between the BookMaster revision tags :rev and :erev).
Note: The revision ID (abc in the example in Figure 248 on page 488) is controlled
by the REVREF process statement—see “REVREF—Revision Code
Reference” on page 433. Subsequent changes to the source can therefore be
separately identified by using different revision IDs (which are associated
with unique revision characters).
UPDSEQ0—Update Sequenced 0
This process option produces a control data set that relates insertions and deletions
to the relative line numbers of the old data set. It is available for the Line compare
type only. UPDSEQ0 is similar to UPDCMS8, but uses relative line numbers
instead of sequence number columns from the old data set.
This update data set is characterized by control statements followed by source lines
from the new data set. All UPDSEQ0 control statements are identified by the
characters ./ in columns 1 and 2 of the 80-byte record, followed by one or more
blanks and additional blank-delimited field s. The control statements are insert (I),
delete (D), replace (R), and comment (*). Control statement data does not extend
beyond column 50. Figure 249 shows an example of a UPDSEQ0 update data set
listing.
The summary totals line has a T in column 1. The summary statistics are located at
fixed offsets in the output line. The data set has a line length of 132 bytes.
In Figure 250, the member is shown in split screen mode. The bottom half of the
screen shows the result of scrolling right to see the remainder of the member.
Table 33 shows the column numbers used to display the update information:
Table 33. UPDSUMO Format Using Line Compare
Column Numbers Data Item
4–11 Number of new lines processed
13–20 Number of old lines processed
22–29 Number of new line insertions
31–38 Number of old line deletions
40–47 Total number of line changes
49–56 Total number of reformats
58–65 Total number of members processed
67–74 Total number of members different
76–83 Total new members not processed
85–92 Total old members not processed
94–101 Total number of new lines that are not to be processed
103–110 Total number of old lines that are not to be processed
In Figure 251, the member is shown in split screen mode. The bottom half of the
screen shows the result of scrolling right to see the remainder of the member.
Table 34 shows the column numbers used to display the update information:
Table 34. UPDSUMO Format Using Word Compare
Column Numbers Data Item
4–11 Number of new words processed
13–20 Number of old words processed
22–29 Number of new word insertions
31–38 Number of old word deletions
40–47 Total number of word changes
49–56 Blank space. No reformat columns are represented in Word compare.
58–65 Total number of members processed
67–74 Total number of members different
76–83 Total new members not processed
85–92 Total old members not processed
In Figure 252, the member is shown in split screen mode. The bottom half of the
screen shows the result of scrolling right to see the remainder of the member.
Table 35 shows the column numbers used to display the update information:
Table 35. UPDSUMO Format Using Byte Compare
Column Numbers Data Item
4–11 Number of new bytes processed
13–20 Number of old bytes processed
22–29 Number of new byte insertions
31–38 Number of old byte deletions
40–47 Total number of byte changes
49–56 Blank space. No reformat columns are represented in Byte compare.
58–65 Total number of members processed
67–74 Total number of members different
76–83 Total new members not processed
85–92 Total old members not processed
IBM may not offer the products, services, or features discussed in this document 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 document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to the IBM
Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY
10504–1785, USA.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries in writing to
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
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.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
IBM Corporation,
Mail Station P300
2455 South Road
Poughkeepsie New York 12601–5400
U.S.A.
The licensed program described in this document 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.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
This publication also documents intended Programming Interfaces that allow the
customer to write programs to obtain the services of ISPF. This information is
identified where it occurs, either by an introductory statement to a chapter or
section or by the following marking:
+---------------------Programming Interface information----------------------+
AD/Cycle GDDM
APL2 IBM
BookManager Language Environment
BookMaster MVS
C++/MVS MVS/XA
COBOL/370 OS/390
Common User Access RACF
CUA SAA
DFSMSrmm Systems Application Architecture
DFSMS/MVS Tivoli
DFSORT VTAM
FFST z/OS
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Other company, product, and service names may be trademarks or service marks
of others.
Notices 497
498 z/OS V1R6.0 ISPF User’s Guide Vol II
Index
Special characters AFTER parameter (continued)
When field 347
Batch (option 5) (continued)
JCL generation for Assembler and
: (colon), using with function key AIX entry in Volume field 153 Linkage Editor 290
definition 45 Alias action, Action column 203 JCL generation for compilers 288
/ (data set name character), Data Set List Alias members, searching 462 Linkage Editor (option 5.7) 294
utility (option 3.4) 164 Alias members, SuperC compare 462 Member Parts List (option 5.12) 297
.* Search-For process statement 437, 457 ALL parameter overview 6
.IM control word 252 FIND command 93 password protection, lack of 287
* Search-For process statement 437, 457 Function field 343 PL/I optimizing compiler (option
*AIX* entry in Volume field 153 Variable field 344 5.5) 293
*PATH* entry in Volume field 153 ALLMEMS 398, 438 processing sequence 286
*VSAM* entry in Volume field 153 allocate action prompt workstation VS COBOL II compiler (option
% field, Data Set List utility 163 command 381 5.2) 291
%Used field, VTOC Summary ALLOCATE command, TSO 123 VS COBOL II interactive debug
Information panel 169 allocate SMS workstation command 382 (option 5.10) 296
%USED keyword, SORT command 182 allocate workstation command 381 VS FORTRAN compiler (option
> (greater than) Allocation Error panel 128 5.3) 292
using with function key definition 45 American National Standard VS Pascal compiler (option 5.6) 293
|, defined for SuperC 472 Institute 199 Batch Assembler H panel 290
&xxxxx action, ACTION column 203 ANYC Search-For process option 438 Batch Linkage Edit panel 295
= (repeat last command) line command, ANYC SuperCE process option 398 Batch Member Parts List panel 297
Data Set List utility (option 3.4) 175 APNDLST Search-For process Batch options
= workstation command 382 option 438 ISPDTLC 298
“To” panel for copying 145 APNDLST SuperCE process option 399 OS/390 C/C++ 298
“To” panel for moving 147 APNDUPD SuperCE process option 399 BATCH parameter, Print Mode field 188
APPC address Batch PL/I Optimizing Compile
definition 69 panel 293
Numerics APPEND command Batch Selection panel 285
3850 virtual volumes Data Set List utility (option 3.4) 176 Batch Selection panel with JCL
allocating a data set to 124 parameters 176 generated 288
5550 terminal 204 Application ID field, Command Table Batch VS COBOL II Compile panel 291
Utility panel 201 Batch VS FORTRAN Compile panel 292
aspect ratio parameter for PRINTG 31 Batch VS Pascal Compile panel 294
A Assembler concatenation sequence 256
Assembler H (option 4.1) allocation data
BEFORE parameter
Breakpoint Primary Option
A (ANSI) parameter, Printer Carriage sets Menu 351
Control field 199 overview 258 When field 347
A (ASA printer characters) record Assembler H (option 5.1) 290 Blank action, Action column 203
format 125 Assembler Options field blank parameter
ACCOUNT command, TSO 124 Foreground Assembler H (option Active field
ACCOUNT, TSO 104 4.1) 259 breakpoints 347
ACTBAR workstation command 381 Attrib display view, Initial View function traces 343
Action column 202 field 154 variable traces 345
Activate/Create Profile DS Name field, DSORG field 163
SuperCE Profile Manager panel 231 Operation field 345
active window frame color 62
AD/Cycle C/370 compiler B Pool field 345
Printer Carriage Control field 199
batch processing 298 B (batch) parameter, Mode field
Select Pack option for “To” data set
foreground processing 281 Search-For Utility panel 235
field 145
Ada/Cycle C/370 compiler SuperC Utility panel 212
Sequence Numbers field 215
batch processing (option 5.15) 298 B (blocked) record format, Record Format
Specify additional search strings
foreground processing (option field 125
field 235
4.15) 280 B (browse) line command
When field 347
Additional IBM Program Development Data Set List utility (option 3.4) 171
blank, SuperC prefix code 472
Products panel 353 Batch (option 5)
BLKS parameter, Space Units field 124
Additional Input Libraries field, AD/Cycle C/370 compiler (option
BLKSZ
Foreground Print Options panel 255 5.16) 298
field 163
address, APPC 69 Ada/Cycle C/370 compiler (option
keyword 182
address, TCP/IP 69 5.15) 298
SORT command 182
AFTER parameter Assembler H (option 5.1) 290
Block size field, Allocate New Data Set
Breakpoint Primary Option C/370 compiler (option 5.13) 297
panel 125
Menu 351
Index 501
DEVICE keyword, SORT command 182 double-byte character set (DBCS) END
device name parameter for PRINTG 31 (continued) Traces (option 7.7) 344, 345
Dialog Function/Selection Panel, finding a 1-byte hexadecimal END command
invoking 313 string 95 Breakpoints (option 7.8) 347, 349
Dialog Services (option 7.6), calling a Format Specification utility (option Command Table utility (option
dialog service 338 3.11) 204 3.9) 203
dialog test DPACMT Search-For process option 438 Dialog Test (option 7) 311
accessing and updating variables 307 DPACMT SuperCE process option 400 Variables (option 7.3) 321
available ISPF facilities 307 DPADCMT Search-For process Enter Session Manager Mode field 302
breakpoint cancel (option C) 305 option 438 Environ settings 64
environment 305 DPADCMT SuperCE process option 400 ENVIRON system command 64
ISPF log generation 307 DPBLKCL Search-For process environment, Dialog Test 305
message displayed for severe option 439 errors
errors 309 DPBLKCL SuperCE process option 400 message displayed during dialog test
NEWPOOL option 308 DPCBCMT Search-For process processing 309
severe error found at breakpoint 309 option 439 reasons for occurring during Dialog
Dialog Test DPCBCMT SuperCE process option 401 Test 309
DBCS value format 325 DPFTCMT Search-For process trigger statement 255
log entry for current value of option 439 EXCLUDE command 177
variable 338 DPFTCMT SuperCE process option 401 Exclude Data Set command 175
modifying a table row 329 DPLINE Search-for process Execution Parms field
reasons errors occur 309 statement 445 COBOL interactive debug 274
variable usage 308 DPLINE SuperC process statement 420 Exit (option 7.X) ending Dialog Test 352
Dialog Test (option 7) DPLINEC Search-For process Exit (option X)
Breakpoints (option 7.8) 345 statement 445 overview 6
commands 309 DPLINEC SuperCE process Expanding Packed Data 251
D (delete lines) 311 statement 420 expansion trigger, defined 252
Dialog Services (option 7.6) 338 DPPLCMT Search-For process Expiration data field, Allocate New Data
environment 350 option 439 Set panel 125
exceptions to restoration when using DPPLCMT SuperCE process option 401 Expires field, Data Set List utility 163
Go (option G) 350 DPPSCMT Search-For process EXPIRES keyword, SORT command 182
Exit (option 7.X) 352 option 439 explosion chain, defined 280
Functions (option 7.1) 313 DPPSCMT SuperCE process option 401 extended binary coded decimal
I (insert lines) 312 DR, defined for SuperC 472 interchange code (EBCDIC)
Log (option 7.5) 336 DS1-DS4 fields defining data type 206
overview 6 Extended Search-For - Concatenation using numbered data 207
Panels (option 7.2) 316 Data Set Entry panel 243 Extended Search-For - Concatenation
R (repeat lines) 312 SuperCE - Concatenation Interactive Batch Entry panel 244
severe error handling 308 Entry panel 226 Extended Search-For - Concatenation
Traces (option 7.7) 341 DSLIST exit 151 Data Set Entry panel 243
Tutorial (option 7.T) 352 DSLIST workstation command 381 Extended Search-For Compare utility
variable usage 308 Dsname Level field, Data Set List Utility applications 395
Variables (option 7.3) 319 panel 151 options
Dialog Test Primary Option Panel 306 Dsorg field, Data Set List utility 163 B - submit batch search-for 244
Directory blocks field, Allocate New Data DSORG keyword, SORT command 182 Blank - search-for strings 243
Set panel 125 DTEST system command 306 E - edit Search-For statements data
DISALLOW_WILDCARDS_IN_HLQ set 245
option 152 P - select Search-For process
DISPLAY command
Browse 90
E options 245
overview 239
E (EBCDIC) parameter, Field Type
parameters process options 397
field 206
CC 91 process statements 407
E (edit data set) line command, Data Set
char 91 return codes 458
List utility (option 3.4) 170
NOCC 91 SuperC program description 394
Edit (option 2)
Display Style Options field, SCRIPT/VS utility differences 393
editing a data set 102
Processor panel 267 Extended Search-For process statements,
overview 6
distributed editing 75 notation conventions 442
valid logical record length 101
DLMDUP SuperCE process option 400 Extended Search-For Utility panel 240
valid record format 101
DLREFM SuperCE process option 400 extended utilities 393
edit action prompt workstation
DM, defined for SuperC 472
command 381
Document Composition Facility
EDIT command, Browse 91
(DCF) 266
double-byte character set (DBCS)
Edit Entry Panel 102 F
Edit workstation command 381 F (foreground) parameter, Mode
column specification in dialog
edit, command table line command 204 field 212
test 326
edit, distributed 75 F (foreground) parameter, Mode field,
defining data type 206
editing a member 119 Search-For Utility panel 235
Dialog Test variables format 323
Index 503
From Table field, Format Specification
panel 169, 206
I ISPF
default keylist 42
FSCR parameter, MODE field 315, 316 I (data set information) line command, restrictions
full information workstation Data Set List utility (option 3.4) 173 multivolume data sets 124, 151
command 381 I (implicit) variable, P (pool) field 321 tape 124, 151
function key defaults, workplace 382, I (insert lines), Dialog Test (option ISPF C/S download 194
383 7) 312 ISPF C/S Download Utility
function key settings, workplace 382 I (insert) line command C/S method 194
function keys Breakpoints (option 7.8) 347 ISPF C/S Install option 192
defining functions 43 Tables (option 7.4) 330, 332 ISPF C/S Install Utility
specifying labels 43 Variables (option 7.3) 321 ISPFINST.EXE 196
specifying number 55 I (insert) line command, Command Table ISPF C/S Installation 192
Functions (option 7.1), testing a dialog utility (option 3.9) 204 ISPF Command field 299
function 313 I, defined for SuperC 472 ISPF command shell 376
IBM Products (option 9) ISPF Command Shell panel 299
overview 6 ISPF command shell workstation
IC, defined for SuperC 472
G IDPFX Search-For process option 440
command 381
ISPF command table workstation
generic unit address 124 IEBCOPY utility 110, 174 command 381
GET operation 345 IEBGENER utility 190 ISPF Primary Option Menu - status
global color change utility 58 If Partitioned, Replace Like-Named area 9
global color change workstation Members field 145 ISPF referral list
command 381 If Sequential, “To” Data Set Disposition Workplace (Option 11) 361
global GUI color change utility 60 field 145 ISPF restrictions
graphics interface mode, effect on Session IM, defined for SuperC 472 multivolume data sets 124, 151
Manager 249 image path 74 tape 124, 151
graphics, settings parameters for implicit variable 321 ISPF Settings (option 0 ), overview 5
PRINTG 31 INCLUDE statement 252 ISPFINST.EXE 196
Groups For Primary Members field inconsistent attributes, defined 128 ISPTLIB 200
Foreground Member Parts List information action prompt workstation ISRFORM table 207
panel 278 command 381 ISRLEMX
Member Parts List Display 280 Information Center Facility description 252
GUI Installation, ISPF C/S Install foreground processing sequence 250 member parts list 276
Utility 192 Hardcopy utility 187 return codes 255
GUI parameters, specifying 65 Outlist utility 199 ISRSCAN
GWCBL SuperCE process option 402 information, bottom-of-listing 475 description 252
Initial Macro field, Edit Entry panel 87 member parts list 289
Initial View field return codes 255
H defined 153 ISU data set organization, DSORG
Hardcopy utility (option 3.6) views field 163
additional batch printing Attrib 154
information 190 sequence of views 153
Space 154
using the TSO/E Information Center
Facility 190 Total 154 J
Volume 154 JCL generation
Hardcopy Utility panel
input data sets 255 Assembler and Linkage Editor 290
after JCL generation 189
insert compose, defined for SuperC 472 compilers 288
before JCL generation 187
insert matching, defined for SuperC 472 job control language, generating and
with the TSO/E Information Center
insert, defined for SuperC 472 submitting print jobs 188
Facility installed 191
INSERT, Traces (option 7.7) 344, 345 job statement information
hashsum, defined 478
Installation preventing JES line counting 269
HELP command
Download Data Set to job stream, submitting a 89, 98
displaying column numbers
Workstation 192 JobID field, Outlist Utility panel 198
searched 93
installation exits Jobname field, Outlist Utility panel 198
HEX command
compress request 110, 174 jump function, from leader dots 29
Browse 95
operands data set allocation 122
DATA 96 data set list (DSLIST) 151
OFF 96 print utility 187, 199, 250 K
ON 96 Installation program K (key) variable 327, 329, 331
VERT 96 Workstation agent 196 KB parameter, Space Units field 124
hexadecimal data, Dialog Test variables integration program, workstation keylist
format 323 tool 75 defaults for Help Panels 42
high-level qualifier IS data set organization, DSORG help panel name 51
wildcards in 152 field 163 modification choices 48
ISPCMDS 200 keylist utility 42
ISPDTLC (Option 4.18) 281 keylist workstation command 381
ISPDTLC compile, batch 298 keys 42
ISPDTLC interface panel 281, 282, 283
Index 505
member parts list display 279 NEWPOOL field 316 Open option field (continued)
member summary listing, SuperC 474 NEXT parameter, FIND command 93 SHR WRITE parameter 335
membered PDS, defined 213 NO parameter WRITE parameter 335
Message field, display view panels 161 Active field OPEN parameter 334, 335
MESSAGE keyword, SORT breakpoints 347 Open workstation command 381
command 182 function traces 343 OPT field 314
message retrieval tool, LookAt xiv variable traces 345 option
mixed data Browse Output field 225 Cancel (option C) 350
B (browse data set) line Confirm Delete Request field, Go (option G) 350
command 171 deselect 155 option selection
defining data type 206 Replace like-named PDS members 0 - ISPF Settings 5
E (edit data set) line command 170 field 145 1 - View 5
using numbered data 207 Select pack option For “To” data set 10 - SCLM 6
V (view data set) line command 171 field 145 2 - Edit 6
Mixed Mode 105 Specify additional search strings field, 3 - Utilities 6
MIXED Search-For process option 440 deselect 235 4 - Foreground 6
MIXED SuperCE process option 402 Table available field 334 5 - Batch 6
Mod parameter, “To” Data Set Table on disk field 335 6 - Command 6
Disposition field 145 NOACTBAR workstation command 381 7 - Dialog Test 6
Mode field NOCC parameter, DISPLAY 9 - IBM Products 6
Search-For Utility panel 235 command 91 X - Exit 6
SuperC Utility panel 212 Nolist parameter, Listing Type field 215, OS/390 C/C++ compile, batch 298
Mode, Mixed 105 223 Other field
MOUNT authority 124 non-paired change, defined for Batch Assembler H (option 5.1) 291
MOVE command 175 SuperC 475 Batch Linkage Editor (option 5.7) 295
move member 119 non-paired members, defined for Batch VS COBOL II compiler (option
Move workstation command 381 SuperC 474 5.2) 292
move/copy 378 NOP action, ACTION column 203 Batch VS FORTRAN compiler (option
Move/Copy utility (option 3.3) NOPRTCC Search-For process 5.3) 292
alias entries 148 option 440 Foreground PL/I optimizing compiler
options NOPRTCC SuperCE process option 403 (option 4.5) 262
C and CP - copying data sets 144 NOSEQ parameter, Sequence Numbers Foreground VS COBOL II compiler
M and MP - moving data field 216 (option 4.2) 260
sets 146 NOSEQ Search-For process option 440 Foreground VS FORTRAN compiler
with load modules 147 NOSEQ SuperCE process option 403 (option 4.3) 261
Move/Copy Utility panel 143 NOSUMS Search-For process option 441 Foreground VS Pascal compiler
Multiple Search Strings panel 236 NOSUMS SuperCE process option 403 (option 4.6) 263
multiple search strings, entering 236 NOT OPEN parameter 334, 335 OTITLE SuperC process statement 428,
multivol indicator 162 NOWRITE parameter 335 452
multivolume data sets 124, 151 NTITLE SuperC process statement 428, OUTDD DD field, SuperC Submit Batch
MVOL, Sort command field 182 452 Jobs panel 219
Number of Copies field, Hardcopy Utility Outlist utility (option 3.8)
panel 191 options
N Blank - display job output 200
D - delete job output from
Name field
display view panels 161 O SYSOUT hold queue 199
L - list job names/IDs via the TSO
NAME keyword object data sets 257
STATUS command 199
LOCATE command 209 Object field
P - print job output and delete
SORT command 182, 210 Foreground VS FORTRAN compiler
from SYSOUT hold queue 199
name, Writer 188 (option 4.3) 261
R - requeue job output to a new
NARROW Super CE process option 402 OCHGT SuperC process statement 424
output class 200
NCHGT Search-For process OFF parameter
Outlist Utility panel 198
statement 450 CONFIRM command 177
overview of ISPF
NCHGT SuperC process statement 424 HEX command 96
ISPF primary options 5
new data set, defined for SuperC SHOWCMD command 180
OVSUM listing type
description 211 old data set, defined for SuperC 467
File comparison of a complete
examples 467 Old DS Name field, SuperCE Utility
PDS 478
used with SuperCE 220 panel 221
File comparison of a sequential data
New DS Name field, SuperCE Utility Old parameter, “To” Data Set Disposition
set or membered PDS 478
panel 221 file 145
OVSUM parameter, Listing Type
New Output Class field, Outlist Utility ON parameter
field 215, 223
panel 199 CONFIRM command 176
New UserID field, Reset ISPF Statistics HEX command 96
panel 184 SHOWCMD command 180
New Version Number field, Reset ISPF Open option field P
Statistics panel 185 NOWRITE parameter 335 P (print) line command
NEWAPPL field 316 SHR NOWRITE parameter 335 Data Set List utility (option 3.4) 174
Index 507
REFMOVR SuperCE process option 403 rules (continued) Search-For utility (option 3.14) (continued)
reformat new, defined for SuperC 472 using the add row option 331 process options (continued)
reformat old, defined for SuperC 472 using the Dialog Test Breakpoints DPCBCMT (ignore COBOL type
REFRESH command 179 option 349 comments) 439
rename 379 using the Modify Row option 329 DPFTCMT (ignore FORTRAN type
rename action prompt workstation comments) 439
command 382 DPPLCMT (ignore PL/I type
Rename Data Set panel 129
rename data set with expiration
S comments) 439
DPPSCMT (ignore PASCAL type
S (information (short)) line command,
date 130 comments) 439
Data Set List utility (option 3.4) 174
rename processing with RACF 130 IDPFX (identifier prefixed) 440
S (select) line command
rename workstation command 381 LMTO (list group members totals
Format Specification utility (option
Rename workstation command 382 only) 440
3.11) 210
renaming data sets LNFMTO (list not found
SCRIPT/VS (option 4.9) 270
with expiration date 130 member/data set totals
S (shared) pool, Pool field 344
REPEAT, Traces (option 7.7) 344, 345 only) 440
S (shared) variable, P (pool) field 321
reset action prompt workstation LONGLN (long lines) 440
S record format, Record Format
command 381 LPSF (list previous Search-For
field 125
RESET command 175, 179 following lines) 440
SAVE command 179
Browse 98 LTO (list totals only) 440
Data Set List utility (option 3.4) 179
Reset ISPF Statistics panel 184 MIXED 440
parameters
Reset ISPF Statistics utility (option 3.5) NOPRTCC (no printer control
list-id 179
options columns) 440
name 210
D - delete ISPF statistics 186 NOSEQ (no sequence numbers -
SCLM (option 10)
R - reset (create/update) ISPF they do not exist) 440
overview 6, 355
statistics 186 NOSUMS (no summary listing
SCLM Primary Option Menu 355
results of resetting statistics 186 section) 441
SCLM Settings 146, 185
valid logical record lengths 183 SDUPM (search duplicate
screen format, specifying 30
RESET key members) 441
SCRIPT/VS (option 4.9) 266
restriction 45 SEQ (sequence numbers - ignore
changing style options 270
reset member 119 columns 73-80) 441
line commands
Reset Mod Level field, Reset ISPF XREF (cross reference strings) 441
D (delete) 270
Statistics panel 185 process statements
S (select) 270
Reset Seq Numbers field, Reset ISPF CMPCOLM (compare
selecting a formatting style 270
Statistics panel 185 columns) 443
using the TSO/E Information Center
reset statistics 374 CMPLINE (compare lines) 444
Facility 271, 272
restrictions on member expansion and DPLINE (don’t process lines) 445
SCRIPT/VS Options for Style panel 271
member parts lists DPLINEC (continuation condition
SCRIPT/VS Processor panel 266
all programming languages 253 of DPLINE) 445
SDUPM Search-For process option 441
assembler 253 LNCT (line count) 447
Search DS Name field, Extended
COBOL 253, 254 LPSFV (count value) 448
Search-For Utility panel 240
FORTRAN 253 LSTCOLM (list columns) 449
Search Member List panel 238
Pascal 253 NCHGT (change text of new text
Search String field, Search-For Utility
PL/I 253 string) 450
panel 235
SCRIPT/VS 254 SELECT (select members/data sets
search strings, multiple 236
RESUME - Dialog Test (option 7) 311 to be searched) 453
Search-For listings, SuperC 479
return codes SLIST (statements data set listing
Search-For process options 438
Batch JCL generation 255, 289 control) 454
Search-For process statements 441
member expansion 255 SRCHFOR (Search-For strings in
Search-For Process Statements panel 246
SuperC 458 the input data sets) 455
Search-For Utility - Submit Batch Jobs
REXX error exits 302 SRCHFORC (continuation
panel 239
REXX/370 compiler condition of SRCHFOR) 455
Search-For utility (option 3.14)
batch processing 297 return codes 458
applications 395
foreground processing 280 selecting members from a member
invoking directly 463
RFIND command 177 list 238
process options
Data Set List utility (option 3.4) 178 SuperC program description 394
ANYC (any case) 438
using 95 utility differences 393
APNDLST (appends the listing to
RN, defined for SuperC 472 Search-For Utility panel 234
a data set) 438
Rnn parameter 347 SearchFor extended workstation
CKPACKL 438
RO, defined for SuperC 472 command 382
COBOL (ignore columns 1–6) 438
rules SearchFor workstation command 382
DPACMT (ignore comment
for substituting slash (/) for data set Secondary quantity field, Allocate New
lines) 438
name 164 Data Set panel 125
DPADCMT (ignore ADA type
for using the col-1 and col-2 Select action, Action column 203
comments) 438
operands 95 SELECT command
DPBLKCL (ignore blank
service call image for function trace Format Specification utility (option
lines) 439
entries 338 3.11) 210
Index 509
SuperC comparison process statements SuperC utility (option 3.12) SuperCE utility (option 3.13) (continued)
(continued) applications 395 process options (continued)
sliding (Y2PAST operand) 436 new data set 211 CNPML (count non-paired
start-position (NEXCLUDE old data set 213 member lines) 399
operand) 426 printing a Search-For listing in batch COBOL (ignore columns 1-6) 399
start-position (NFOCUS mode 239 DLMDUP (don’t list matching
operand) 427 printing a SuperC listing in batch duplicate lines) 400
start-position (OEXCLUDE mode 217 DLREFM (don’t list old data set
operand) 426 process options 397 reformatted lines) 400
start-position (OFOCUS process statements 407 DPACMT (ignore comment
operand) 427 program description 394 lines) 400
SuperC Defaults panel 233 return codes 458 DPADCMT (ignore ADA type
SuperC extended workstation specifying members on a member comments) 400
command 382 list 216 DPBLKCL (ignore blank
SuperC listing prefix codes submit options lines) 400
| 472 1 - generate output listing in DPCBCMT (ignore COBOL type
blank 472 DATA SET NAME 218 comments) 401
D 472 2 - generate output listing using DPFTCMT (ignore FORTRAN type
DC 472 completed //OUTDD DD 219 comments) 401
DM 472 blank - generate output listing to DPPLCMT (ignore PL/I type
DR 472 SYSOUT CLASS 218 comments) 401
I 472 utility differences 393 DPPSCMT (ignore PASCAL type
IC 472 SuperC Utility panel 211 comments) 401
IM 472 SuperC utility, requirements for 394 FMVLNS (flagged moved
MC 472 SuperC workstation command 382 lines) 402
RN 472 SuperC, DBCS considerations 211 GWCBL (generate change
RO 472 SuperCE - Concatenation Batch Entry bars) 402
SuperC listing source data 468 panel 227 LMCSFC (list name, number of
SuperC listing types SuperCE - Concatenation Interactive bytes, and hashum) 402
CHNG 215, 223 Entry panel 226 LOCS (list only changed members
Delta 214, 223 SuperCE - Profile Manager panel or data sets) 402
Long 215, 223 option A - Activate 231 LONGLN (create listing with 203
Nolist 215, 223 option C - Create 231 columns) 402
OVSUM 215, 223 option D - Defaults 232 MIXED 402
SuperC listings SuperCE Compare utility NARROW (create listing with 132
overview 467 CKPACKL 399 columns) 402
prefix codes 472 UPDLDEL Long source and Delta NOPRTCC (no printer control
source and index listings 467 data set 485 columns) 403
SuperC load module compares 463 UPDLDEL prefixed Delta data NOSEQ (no sequence
SuperC Member List panel 216 set 486 numbers--they do not exist) 403
SuperC process options SuperCE process statements, notation NOSUMS (no summary listing
APNDUPD 480 conventions 407 section) 403
UPDCMS8 481 SuperCE Profile Browse Display overview 397
UPDCNTL 481 panel 230 REFMOVR (reformat
UPDMVS8 485 SuperCE utility (option 3.13) override) 403
UPDPDEL 486 applications 395 SEQ (sequence numbers--ignore
UPDSEQ0 489 options columns 73-80) 403
UPDSUMO 490 A - activate profiles and UPDCMS8 (update CMS 8
SuperC Process Statements panel 229 defaults 229 format) 403
SuperC program, requirements for 394 B - submit batch data set UPDCNTL (update control) 404
SuperC programming interface 232 compare 226 UPDLDEL (source data set with
SuperC search process options Blank - compare data sets 225 delta changes) 404
DPCPCMT 401, 439 E - edit SuperCE statements data UPDMVS8 (update MVS 8
DPMACMT 401, 439 set 228 format) 405
FINDALL 440 P - select process options 397 UPDPDEL (update prefix delta
FMSTOP 402, 440 P - select SuperCE process lines) 405
SuperC type-of-difference codes options 227 UPDSEQ0 (update sequence
LEN 473 S - Extended Search-For 0) 406
N-LN# and O-LN# 473 utility 239 UPDSUMO (update summary
types 472 process options only) 406
SuperC update files ANYC (any case) 398 WIDE (side-by-side list with 202
UPDREV 487, 488 APNDLST (appends the listing to columns) 406
UPDREV2 Revision File (2) 489 a data set) 399 XWDCMP (extended word
SuperC Utility - Submit Batch Jobs panel APNDUPD (append update compare) 406
overview 217 output) 399 process statements 407
using NOLIST 220 CKPACKL (check for packed return codes 458
data) 399 SuperC program description 394
Index 511
UPDCNTL update data set and Variables (option 7.3) (continued) word, defined for SuperC 223
formats 481 working with dialog variables 319 Workplace (Option 11)
UPDLDEL SuperCE process option 404 Verb column 202 action bar choices 362
UPDMVS8 SuperCE process option 405, VERT parameter, HEX command 96 file 362
485 View (option 1) options 370
UPDPDEL SuperCE process option 405, description 85 space 370
486 View Entry Panel 85 SuperC 372
UPDPDEL update data set 486 view action prompt workstation test 372
UPDSEQ0 SuperCE process option 406, command 382 view 369
489 VIEW command, Browse 98 actions that require prompt
UPDSEQ0 update data set 489 view output mode 213, 225, 235, 245 windows 373
UPDSUMO SuperCE process View workstation command 382 ISPF command shell 376
option 406, 490 view, command table line command 204 move/copy 378
UPDSUMO update data set 490 viewing a member 119 rename 379
user-defined trigger 252 Volume DATA field, VTOC Information reset statistics 374
Utilities (option 3) Display 168 TSO command 374
Command Table utility (option Volume display view, Initial View WS command 375
3.9) 200 field 154 commands 381
Data Set List utility (option 3.4) 150 Volume field entry panels 359
Data Set utility (option 3.2) 119 Data Set List utility 162 data set view 360
Format Specification utility (option Data Set List Utility panel 153 library view 360
3.11) 204 VOLUME keyword, SORT example scenario 387
Hardcopy utility (option 3.6) 187 command 182 ISPF Library field 360
ISPF C/S Install (option 3.7) 192 Volume Serial 104 ISPF referral lists 361
Library utility (option 3.1) 108 Volume Serial field Object Name field 361
Move/Copy utility (option 3.3) 142 Allocate New Data Set panel 123 overview 359
Outlist utility (option 3.8) 197 volume, DASD 104 specifying actions 362
overview 6 VS COBOL II compiler (option 4.2) Workplace example 387
Reset ISPF Statistics utility (option overview 259 workplace function keys 382, 383
3.5) 183 VS COBOL II compiler (option 5.2) 291 Workplace option description 6
Search-For utility (option 3.14) 233 VS COBOL II interactive debug (option workplace settings 383
SuperC utility (option 3.12) 210 4.10) 272 workplace settings command 382
SuperCE utility (option 3.13) 220 VS COBOL II interactive debug (option Workstation agent 196
Utility Selection Panel 107 5.10) 296 installation program 196
utility differences VS COBOL II Interactive Debug Workstation Commands
extended 393 panel 296 = 382
standard 393 VS command, Data Set List utility (option ACTBAR action prompt 381
Utility Selection Panel 107 3.4) 183 allocate 381
VS data set organization, DSORG allocate action prompt 381
field 163 allocate SMS 382
V VS FORTRAN compiler (option 4.3) 260
VS FORTRAN compiler (option 5.3) 292
Browse 381
catalog 381
V (VDEFINE) variable, P (pool)
VS Pascal compiler (option 4.6) 262 command action prompt 381
field 321
VS Pascal compiler (option 5.6) 293 compress 382
V (view data set) line command, Data Set
VS-E 163 Copy 381
List utility (option 3.4) 171
VSAM entry in Volume field 153 CUA attributes 381
V record format, Record Format
VSAM workstation command 382 delete 381
field 125
VT command, Data Set List utility Delete 381
VA command, Data Set List utility
(option 3.4) 183 delete action prompt 381
(option 3.4) 183
VTOC Data field, VTOC Information DSLIST 381
Variables (option 7.3)
Display 169 Edit 381
CANCEL primary command 321
VTOC information display 168 edit action prompt 381
creating new variables 322
VTOC summary workstation full information action prompt 381
D (delete) line command 321
command 381 global color change 381
DBCS data 323
VV command, Data Set List utility information action prompt 381
deleting variables 322
(option 3.4) 183 ISPF command shell 381
END primary command 321
ISPF command table 381
hexadecimal data 323
keylist 381
I (insert) line command 321
input errors 322 W list action prompt 381
list view 381
LOCATE primary command 321 WE workstation command 382
locate 381
manipulating variables 322 WEW workstation command 382
Member list 381
primary commands 321 WIDE SuperCE process option 406
Move 381
split-screen mode 323 wildcard characters 151
NOACTBAR action prompt 381
test mode 322 window frame color 62
Open 381
usage notes 322, 323 Word parameter
personal data set lists 381
variable life 323 Compare Type field 222
personal library lists 381
variable value 323 FIND command 92
X
X (print index listing) line command,
Data Set List utility (option 3.4) 175
XREF Search-For process option 441
XT field, Data Set list utility 163
XT keyword, SORT command 182
XWDCMP SuperCE process option 406
Y
YES parameter
Active field 343, 345, 347
BROWSE Output field 225
Confirm Delete Request field,
select 155
Index 513
514 z/OS V1R6.0 ISPF User’s Guide Vol II
Readers’ Comments — We’d Like to Hear from You
Interactive System Productivity Facility (ISPF)
User’s Guide Volume II
z/OS Version 1 Release 6.0
Overall, how satisfied are you with the information in this book?
How satisfied are you that the information in this book is:
When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any
way it believes appropriate without incurring any obligation to you.
Name Address
Company or Organization
Phone No.
___________________________________________________________________________________________________
Readers’ Comments — We’d Like to Hear from You Cut or Fold
SC34-4823-03 Along Line
_ _ _ _ _ _ _Fold
_ _ _and
_ _ _Tape
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Please
_ _ _ _ _do
_ _not
_ _ staple
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _Fold
_ _ _and
_ _ Tape
______
NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES
IBM Corporation
Department J87/D325
555 Bailey Avenue
San Jose, CA
U.S.A. 95141-9989
_________________________________________________________________________________________
Fold and Tape Please do not staple Fold and Tape
Cut or Fold
SC34-4823-03 Along Line
Printed in USA
SC34-4823-03