Interactive System Productivity Facility (ISPF) Software Configuration and Library Manager (SCLM) Project Manager’s and Developer’s Guide z/OS Version 1 Release 6.0 SC34-4817-03
Interactive
System
Productivity
Facility
(ISPF)
Software
Configuration
and
Library
Manager
(SCLM)
Project
Managers
and
Developers
Guide
z/OS
Version
1
Release
6.0
SC34-4817-03
Interactive
System
Productivity
Facility
(ISPF)
Software
Configuration
and
Library
Manager
(SCLM)
Project
Managers
and
Developers
Guide
z/OS
Version
1
Release
6.0
SC34-4817-03
Note
Before
using
this
document,
read
the
general
information
under
Notices
on
page
315.
Fourth
Edition
(September
2004)
This
edition
applies
to
ISPF
for
Version
1
Release
6.0
of
the
licensed
program
z/OS
(program
number
5694-A01)
and
to
all
subsequent
releases
and
modifications
until
otherwise
indicated
in
new
editions.
Order
publications
by
phone
or
fax.
IBM
Software
Manufacturing
Solutions
takes
publication
orders
between
8:30
a.m.
and
7:00
p.m.
eastern
standard
time
(EST).
The
phone
number
is
(800)
879-2755.
The
fax
number
is
(800)
284-4721.
You
can
also
order
publications
through
your
IBM
representative
or
the
IBM
branch
office
serving
your
locality.
Publications
are
not
stocked
at
the
address
below.
A
form
for
comments
appears
at
the
back
of
this
publication.
If
the
form
has
been
removed,
and
you
have
ISPF-specific
comments,
address
your
comments
to:
IBM
Corporation
Department
J87/D325
555
Bailey
Avenue
San
Jose,
CA
95141-1003
U.S.A.
Internet:
If
you
would
like
a
reply,
be
sure
to
include
your
name,
address,
telephone
number,
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
1990,
2004.
All
rights
reserved.
US
Government
Users
Restricted
Rights
Use,
duplication
or
disclosure
restricted
by
GSA
ADP
Schedule
Contract
with
IBM
Corp.
Contents
Preface
.
.
.
.
.
.
.
.
.
.
.
.
.
. vii
Who
Should
Use
This
Document
.
.
.
.
.
.
. vii
What
Is
In
This
Document?
.
.
.
.
.
.
.
.
. vii
Using
LookAt
to
look
up
message
explanations
.
. viii
Summary
of
Changes
.
.
.
.
.
.
.
. xi
ISPF
Product
and
Library
changes
.
.
.
.
.
.
. xi
ISPF
Dialog
Manager
component
changes
.
.
.
. xi
Dialog
Tag
Language
(DTL)
changes
.
.
.
.
. xii
ISPF
Component
changes
.
.
.
.
.
.
.
. xii
ISPF
SCLM
Component
changes
.
.
.
.
.
.
. xii
ISPF
Client/Server
Component
changes
.
.
.
. xiii
ISPF
Migration
Considerations
.
.
.
.
.
.
.
. xiii
Migrating
from
Previous
Versions
of
SCLM
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. xv
FLMCPYLB
Statements
Required
for
IOTYPE=A
.
. xv
Versioning
Data
Sets
.
.
.
.
.
.
.
.
.
.
. xv
Year
2000
Support
.
.
.
.
.
.
.
.
.
.
.
. xv
Load
Module
Accounting
Records
and
SSI
Information
.
.
.
.
.
.
.
.
.
.
.
.
.
. xvi
Whats
in
the
z/OS
V1R6.0
ISPF
library?
.
.
.
.
.
.
.
.
.
.
.
.
.
. xvii
z/OS
V1R6.0
ISPF
.
.
.
.
.
.
.
.
.
.
.
. xvii
The
ISPF
User
Interface
.
.
.
.
.
.
. xix
Some
Terms
You
Should
Know
.
.
.
.
.
.
. xix
How
to
Navigate
in
ISPF
Using
the
Action
Bar
Interface
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. xx
Action
Bars
.
.
.
.
.
.
.
.
.
.
.
.
. xx
Command
Nesting
.
.
.
.
.
.
.
.
.
. xxii
Action
Bar
Choices
.
.
.
.
.
.
.
.
.
. xxiii
Point-and-Shoot
Text
Fields
.
.
.
.
.
.
. xxiv
Function
Keys
.
.
.
.
.
.
.
.
.
.
.
. xxv
Selection
Fields
.
.
.
.
.
.
.
.
.
.
. xxvi
How
to
Navigate
in
ISPF
without
Using
Action
Bars
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. xxvi
Part
1.
Project
Managers
Guide
.
.
. 1
Chapter
1.
Defining
the
Project
Environment
.
.
.
.
.
.
.
.
.
.
.
.
. 3
Overview
of
Project
Manager
Tasks
.
.
.
.
.
.
. 3
Project
Definition
Data
.
.
.
.
.
.
.
.
.
. 3
Generating
a
Project
Environment
.
.
.
.
.
.
. 3
Step
1:
Determine
the
Projects
Hierarchy
.
.
.
.
. 4
Primary
Non-Key
Group
Testing
Techniques
.
.
. 6
Step
2:
Identify
the
Types
of
Data
to
Support
.
.
. 8
Step
3:
Establish
Authorization
Codes
.
.
.
.
.
. 8
Using
Authorization
Codes
to
Control
SCLM
Operations
.
.
.
.
.
.
.
.
.
.
.
.
.
. 9
Allowing
Parallel
Updates
.
.
.
.
.
.
.
. 11
Step
4:
Allocate
the
PROJDEFS
Data
Sets
.
.
.
. 12
Step
5:
Allocate
the
Project
Partitioned
Data
Sets
.
. 13
Data
Set
Naming
Conventions
.
.
.
.
.
.
. 13
Flexible
Naming
of
Project
Partitioned
Data
Sets
13
Number
of
Data
Sets
to
Allocate
.
.
.
.
.
. 14
Versioning
Partitioned
Data
Sets
.
.
.
.
.
. 17
Project
Partitioned
Data
Sets
.
.
.
.
.
.
.
. 18
Space
Considerations
.
.
.
.
.
.
.
.
.
. 18
Step
6:
Allocate
and
Create
the
Control
Data
Sets
.
. 18
Create
the
Accounting
Data
Sets
.
.
.
.
.
. 19
Create
the
Export
Data
Sets
.
.
.
.
.
.
.
. 21
Create
the
Audit
Control
Data
Sets
.
.
.
.
. 21
Step
7:
Protect
the
Project
Environment
.
.
.
.
. 23
PROJDEFS
Data
Sets
.
.
.
.
.
.
.
.
.
. 24
Project
Partitioned
Data
Sets
.
.
.
.
.
.
.
. 24
Control
Data
Sets
.
.
.
.
.
.
.
.
.
.
. 24
Step
8:
Create
the
Project
Definition
.
.
.
.
.
. 24
Alternate
Project
Definitions
.
.
.
.
.
.
.
. 25
Create
the
Hierarchy
Definition
.
.
.
.
.
.
. 26
Set
the
Project
Control
Options
.
.
.
.
.
.
. 27
Define
the
Language
Definitions
.
.
.
.
.
. 34
Step
9:
Assemble
and
Link
the
Project
Definition
.
. 40
Assemble
and
Link
Example
.
.
.
.
.
.
. 41
Project
Manager
Scenario
.
.
.
.
.
.
.
.
.
. 41
Prerequisites
for
Defining
an
SCLM
Project
.
.
. 41
Example
Project
Overview
.
.
.
.
.
.
.
. 42
Preparing
the
Example
Project
Hierarchy
.
.
. 44
Understanding
the
Sample
Project
Definition
.
. 47
Preparing
the
Example
Project
Data
.
.
.
.
. 48
Chapter
2.
User
Exits
.
.
.
.
.
.
.
. 51
Specify
the
Change
Code
Verification
Routine
.
.
. 53
Change
Code
Verification
Routine
Example
.
.
. 54
Specify
the
Build
and
Promote
User
Exit
Routines
56
Build
and
Promote
User
Exit
Routine
Requirements
.
.
.
.
.
.
.
.
.
.
.
.
. 56
Build
and
Promote
User
Exit
Output
Data
Sets
.
. 58
Specify
the
Audit
Version
Delete
User
Exit
Routine
59
Audit
Version
Delete
User
Exit
Routine
Requirements
.
.
.
.
.
.
.
.
.
.
.
.
. 59
Specify
the
Delete
User
Exit
Routine
.
.
.
.
.
. 60
Delete
User
Exit
Routine
Requirements
.
.
.
. 61
Delete
User
Exit
Output
Data
Set
.
.
.
.
.
. 62
User
Exit
Routine
Example
.
.
.
.
.
.
.
.
. 63
Chapter
3.
Additional
Project
Manager
Tasks
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 67
Splitting
Project
VSAM
Data
Sets
.
.
.
.
.
.
. 67
Backing
Up
and
Recovering
the
Project
Environment
68
Synchronizing
Accounting
Data
Sets
.
.
.
.
.
. 68
Maintaining
Accounting
Data
Sets
.
.
.
.
.
.
. 69
Modifying
the
Delete
Group
Dialog
Interface
.
.
. 69
Implementing
Package
Backout
.
.
.
.
.
.
.
. 70
Copyright
IBM
Corp.
1990,
2004
iii
Chapter
4.
Converting
Projects
to
SCLM
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 73
Prerequisites
for
Existing
Hierarchies
.
.
.
.
.
. 73
Create
Alternate
Project
Definitions
.
.
.
.
.
. 73
Create
Architecture
Definitions
for
the
Project
.
.
. 74
Register
Existing
PDS
Members
with
SCLM
.
.
. 74
Introducing
Fixes
to
the
Converted
Hierarchy
.
.
. 75
Chapter
5.
Language
Definition
Considerations
.
.
.
.
.
.
.
.
.
.
. 77
Using
Multiple
Translators
in
a
Language
Definition
78
Invoking
User-Defined
Parsers
.
.
.
.
.
.
.
. 81
Defining
Information
Tracked
by
SCLM
.
.
.
. 81
Writing
the
Parser
.
.
.
.
.
.
.
.
.
.
. 81
Telling
SCLM
How
to
Invoke
Your
Parser
.
.
. 82
Processing
Conditionally
Saved
Components
.
.
. 92
Example
of
Processing
Conditionally
Saved
Components
.
.
.
.
.
.
.
.
.
.
.
.
. 92
Setting
Up
the
Project
Definition
.
.
.
.
.
. 93
Specifying
the
Locations
of
Included
Members
.
. 94
Example
.
.
.
.
.
.
.
.
.
.
.
.
.
. 95
Dynamic
Include
Tracking
.
.
.
.
.
.
.
.
. 99
Input
List
Translators
.
.
.
.
.
.
.
.
.
.
. 100
Configuring
the
Input
List
Translators
.
.
.
. 100
Defining
a
New
Language
to
SCLM
.
.
.
.
.
. 101
Using
DDnames
and
DDname
Substitution
Lists
101
Showing
Users
How
to
Write
CC
Architecture
Definitions
.
.
.
.
.
.
.
.
.
.
.
.
.
. 111
Convert
Your
JCL
Decks
to
Architecture
Definitions
.
.
.
.
.
.
.
.
.
.
.
.
. 112
Defining
a
Preprocessor
to
SCLM
.
.
.
.
.
.
. 113
Passing
the
Source
to
the
Compiler
.
.
.
.
. 115
Converting
JCL
to
SCLM
Language
Definitions
.
. 118
Before
You
Begin
.
.
.
.
.
.
.
.
.
.
. 118
Capabilities
and
Restrictions
.
.
.
.
.
.
. 118
Converting
JCL
Cards
to
SCLM
Macro
Statements
.
.
.
.
.
.
.
.
.
.
.
.
. 120
Chapter
6.
Using
SCLM
and
Tivoli
Information
Management
for
z/OS
.
. 129
Required
Environment
.
.
.
.
.
.
.
.
.
. 129
Description
of
User
Program
Interaction
.
.
.
. 129
Input
Parameters
.
.
.
.
.
.
.
.
.
.
.
. 129
Option
List
Format
.
.
.
.
.
.
.
.
.
. 129
Information
Management
Parameters
.
.
.
. 130
SCLM
Parameters
.
.
.
.
.
.
.
.
.
.
. 131
Program
Flow
.
.
.
.
.
.
.
.
.
.
.
.
. 131
Error
Processing
.
.
.
.
.
.
.
.
.
.
.
. 131
Example
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 132
Chapter
7.
Understanding
and
Using
the
Customizable
Parsers
.
.
.
.
.
. 133
The
Parsers
as
Shipped
.
.
.
.
.
.
.
.
.
. 133
Sample
Language
Definitions
.
.
.
.
.
.
. 133
Parser
Error
Listings
.
.
.
.
.
.
.
.
.
. 134
Modifying
the
Parsers
.
.
.
.
.
.
.
.
.
. 134
Adding
More
Elaborate
Parsing
Error
Messages
134
Appending
to
the
Error
Listing
File
.
.
.
.
. 136
Compiling
the
Parsers
.
.
.
.
.
.
.
.
.
. 137
Part
2.
Developers
Guide
.
.
.
.
. 139
Chapter
8.
The
Software
Configuration
and
Library
Manager
.
.
.
.
.
.
.
. 141
SCLM
Project
Environment
.
.
.
.
.
.
.
.
. 141
User
Application
Data
.
.
.
.
.
.
.
.
. 141
Chapter
9.
Using
SCLM
Functions
.
. 145
Name
Retrieval
with
the
NRETRIEV
command
.
. 145
SCLM
Considerations
for
NRETRIEV
.
.
.
. 146
SCLM
Main
Menu
.
.
.
.
.
.
.
.
.
.
.
. 147
SCLM
Main
Menu
Options
.
.
.
.
.
.
.
. 148
SCLM
Main
Menu
Action
Bar
Choices:
.
.
.
. 148
SCLM
Main
Menu
Panel
Fields:
.
.
.
.
.
. 149
View
(Option
1)
.
.
.
.
.
.
.
.
.
.
.
. 149
SCLM
View
-
Entry
Panel
Action
Bar
Choices
150
Edit
(Option
2)
.
.
.
.
.
.
.
.
.
.
.
.
. 152
SCLM
Edit
-
Entry
Panel
Fields
.
.
.
.
.
. 153
Comparison
of
SCLM
and
ISPF
Editors
.
.
.
. 154
SCLM
Command
Macros
.
.
.
.
.
.
.
. 155
Utilities
(Option
3)
.
.
.
.
.
.
.
.
.
.
. 159
Library
Utility
.
.
.
.
.
.
.
.
.
.
.
. 160
Migration
Utility
.
.
.
.
.
.
.
.
.
.
. 176
Database
Contents
Utility
.
.
.
.
.
.
.
. 178
Architecture
Report
Utility
.
.
.
.
.
.
.
. 188
Export
Utility
.
.
.
.
.
.
.
.
.
.
.
. 195
Import
Utility
.
.
.
.
.
.
.
.
.
.
.
. 199
Audit
and
Version
Utility
.
.
.
.
.
.
.
. 203
Delete
Group
Utility
.
.
.
.
.
.
.
.
.
. 214
Package
Backout
Utility
.
.
.
.
.
.
.
.
. 218
Unit
of
Work
Utility
.
.
.
.
.
.
.
.
.
. 225
SCLM
Explorer
.
.
.
.
.
.
.
.
.
.
.
. 234
Build
(Option
4)
.
.
.
.
.
.
.
.
.
.
.
. 236
Build
Report
Example
.
.
.
.
.
.
.
.
. 240
Promote
(Option
5)
.
.
.
.
.
.
.
.
.
.
. 242
Promote
Report
.
.
.
.
.
.
.
.
.
.
. 245
Processing
Errors
.
.
.
.
.
.
.
.
.
.
. 248
Command
(Option
6)
.
.
.
.
.
.
.
.
.
.
. 249
Easy
Cmds
(Option
6A)
.
.
.
.
.
.
.
.
.
. 249
Batch
Processing
.
.
.
.
.
.
.
.
.
.
.
. 249
Output
Disposition
.
.
.
.
.
.
.
.
.
.
. 250
Sample
Project
Utility
(Option
7)
.
.
.
.
.
.
. 251
Chapter
10.
Development
Scenario
253
Understanding
the
Hierarchy
and
the
SCLM
Main
Menu
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 253
Understanding
the
Architecture
Definition
.
.
.
. 254
Sample
SCLM
Development
Cycle
.
.
.
.
.
. 256
Using
the
SCLM
Editor
.
.
.
.
.
.
.
.
.
. 258
Understanding
the
Library
Utility
.
.
.
.
.
. 259
Using
Build
.
.
.
.
.
.
.
.
.
.
.
.
.
. 260
Editing
the
Member
to
Correct
Errors
.
.
.
.
. 261
Attempting
to
Promote
a
Member
before
Performing
a
Build
.
.
.
.
.
.
.
.
.
.
. 261
Rebuilding
the
Changed
Member
.
.
.
.
.
.
. 261
Using
the
Database
Contents
Utility
.
.
.
.
.
. 262
Promoting
a
Member
Successfully
.
.
.
.
.
. 263
Drawing
Down
a
Promoted
Member
.
.
.
.
. 264
Performing
Project
Housekeeping
Activities
.
.
. 264
iv
z/OS
V1R6.0
ISPF
SCLM
Project
Managers
and
Developers
Guide
|
|
|
|
|
|
Chapter
11.
Architecture
Definition
265
Architecture
Members
.
.
.
.
.
.
.
.
.
. 265
Kinds
of
Architecture
Members
.
.
.
.
.
. 265
Defining
Compiler
Processed
Components
.
.
. 266
Compilation
Control
Architecture
Members
.
. 266
Specifying
Source
Members
.
.
.
.
.
.
. 267
Defining
Link-Edit
Processed
Components
.
.
. 267
SCLM
Build
and
Control
Timestamps
.
.
.
. 268
Defining
Application
and
Subapplication
Components
.
.
.
.
.
.
.
.
.
.
.
.
.
. 269
Generic
Architecture
Members
.
.
.
.
.
.
.
. 269
Build
and
Promote
by
Change
Code
.
.
.
.
.
. 270
Architecture
Statements
.
.
.
.
.
.
.
.
.
. 272
Statement
Format
.
.
.
.
.
.
.
.
.
.
. 272
Statement
Uses
.
.
.
.
.
.
.
.
.
.
.
. 273
Sample
Application
Using
Architecture
Definitions
279
Ensuring
Synchronization
with
Architecture
Definitions
.
.
.
.
.
.
.
.
.
.
.
.
.
. 282
Build
Outputs
.
.
.
.
.
.
.
.
.
.
.
.
. 284
Multiple
Build
Outputs
.
.
.
.
.
.
.
.
. 284
Sequential
Build
Outputs
.
.
.
.
.
.
.
. 284
Default
Output
Member
Names
.
.
.
.
.
. 284
Languages
of
Output
Members
.
.
.
.
.
. 285
Chapter
12.
Managing
Complex
Projects
.
.
.
.
.
.
.
.
.
.
.
.
.
. 287
Impact
Assessment
Techniques
.
.
.
.
.
.
. 287
Dependency
Processing
.
.
.
.
.
.
.
.
.
. 287
Propagating
Applications
to
Other
Databases
.
.
. 288
Part
3.
DB2
and
Workstation
Support
.
.
.
.
.
.
.
.
.
.
.
.
. 291
Chapter
13.
SCLM
Support
for
DB2,
General
Information
.
.
.
.
.
.
.
. 293
Restrictions
.
.
.
.
.
.
.
.
.
.
.
.
.
. 293
Information
For
The
Project
Manager
.
.
.
.
. 294
Generating
a
Project
Environment
.
.
.
.
. 294
Information
For
The
Developer
.
.
.
.
.
.
. 296
Developer
Recommendations
.
.
.
.
.
.
. 296
Getting
Started
.
.
.
.
.
.
.
.
.
.
.
.
. 296
Create
DB2
CLIST
.
.
.
.
.
.
.
.
.
.
. 296
Chapter
14.
SCLM
Support
for
Workstation
Builds
.
.
.
.
.
.
.
.
. 299
Requirements
.
.
.
.
.
.
.
.
.
.
.
.
. 299
Overview
of
Workstation
Build
.
.
.
.
.
.
. 299
Information
For
The
Project
Manager
.
.
.
.
. 301
Project
Setup
Considerations
.
.
.
.
.
.
. 301
Information
For
The
Developer
.
.
.
.
.
.
. 304
Migrating
Applications
into
SCLM
.
.
.
.
. 304
Architecture
Definition
Members
for
Workstation
Applications
.
.
.
.
.
.
.
. 305
Specifying
Options
.
.
.
.
.
.
.
.
.
. 307
Including
Outputs
From
Other
Build
Steps
.
. 307
Running
Multiple
Workstation
Commands
.
. 307
Sample
Language
Definition
.
.
.
.
.
.
.
. 308
Workstation
Setup
.
.
.
.
.
.
.
.
.
.
.
. 312
Directories
and
File
Names
.
.
.
.
.
.
.
. 312
Multiple
Builds
on
One
Workstation
.
.
.
.
.
. 313
Notices
.
.
.
.
.
.
.
.
.
.
.
.
.
. 315
Programming
Interface
Information
.
.
.
.
.
. 316
Trademarks
.
.
.
.
.
.
.
.
.
.
.
.
.
. 317
Glossary
of
SCLM
Terms
.
.
.
.
.
. 319
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 323
Contents
v
vi
z/OS
V1R6.0
ISPF
SCLM
Project
Managers
and
Developers
Guide
Preface
This
document
provides
reference
and
usage
information,
along
with
conceptual
and
functional
descriptions
of
the
Software
Configuration
and
Library
Manager
(SCLM).
This
document
also
contains
step-by-step
information
for
setting
up
and
maintaining
an
SCLM
project
environment.
It
describes
how
to
establish
and
monitor
a
database
and
explains
the
library
functions.
Who
Should
Use
This
Document
This
document
is
for
application
developers
whose
projects
are
controlled
by
SCLM.
This
document
is
also
for
project
managers
who
use
SCLM
to
manage
the
development
process.
What
Is
In
This
Document?
This
manual
assumes
that
you
are
familiar
with
the
operation
of
ISPF
in
the
z/OS
environment.
Part
1
of
this
document
is
the
Project
Managers
Guide:
Chapter
1,
Defining
the
Project
Environment,
describes
how
to
generate
a
project
definition.
It
explains
the
steps
that
enable
you
to
create
the
database
that
best
meets
the
needs
of
your
project.
The
chapter
includes
step-by-step
instructions
for
setting
up
the
SCLM
sample
project
included
with
the
ISPF
product.
After
completing
the
steps
described
in
this
chapter,
you
can
experiment
with
basic
SCLM
operations
using
the
sample
project
hierarchy.
Chapter
2,
User
Exits,
describes
the
customization
of
user
exit
points
so
that
SCLM
can
be
integrated
with
other
products.
The
chapter
lists
the
available
exit
routines
and
describes
how
you
can
customize
these
for
your
users.
Chapter
3,
Additional
Project
Manager
Tasks,
describes
additional
tasks
that
project
managers
perform
to
maintain
SCLM
projects.
This
chapter
discusses
backing
up
and
recovering
a
project
database,
using
authorization
codes
to
control
SCLM
operations,
developing
and
maintaining
projects
concurrently,
and
implementing
verification
and
exit
routines
for
SCLM
projects.
Chapter
4,
Converting
Projects
to
SCLM,
describes
the
steps
required
to
convert
existing
ISPF
software
development
projects
to
SCLM.
Chapter
5,
Language
Definition
Considerations
describes
setup
operations
you
must
perform
to
create
a
language
definition
for
SCLM
to
use.
The
subsection
Defining
a
New
Language
to
SCLM
describes
the
control
structures
used
to
manage
SCLM
functions
and
illustrates
how
to
define
new
languages.
It
also
contains
information
on
converting
JCL
decks
to
language
definitions.
Chapter
6,
Using
SCLM
and
Tivoli
Information
Management
for
z/OS,
illustrates
the
interaction
between
SCLM
and
Information
Manager
through
the
use
of
a
sample
program.
Chapter
7,
Understanding
and
Using
the
Customizable
Parsers,
describes
the
REXX
parsers
supplied
with
SCLM
and
provides
examples
of
how
to
customize
them.
Part
2
of
this
document
is
the
Developers
Guide:
Copyright
IBM
Corp.
1990,
2004
vii
Chapter
8,
The
Software
Configuration
and
Library
Manager,
provides
information
on
the
SCLM
project
database
and
the
terminology
used.
The
chapter
describes
the
library
structure
and
naming
conventions
used
when
you
define
and
maintain
SCLM
projects.
Chapter
9,
Using
SCLM
Functions,
describes
how
to
use
the
ISPF
dialog
interface,
select
SCLM
functions
to
retrieve
or
process
certain
information,
and
generate
reports
on
the
information
stored
in
project
databases.
It
also
describes
information
stored
in
accounting,
cross-reference,
and
intermediate
records
for
members
in
the
project
databases.
Chapter
10,
Development
Scenario,
is
a
programmer
scenario
that
describes
the
tasks
typically
performed
by
SCLM
users.
This
chapter
provides
step-by-step
instructions
on
how
to
use
the
basic
SCLM
functions
to
control
development
projects.
Chapter
11,
Architecture
Definition,
describes
architecture
configuration
and
dependency
control
statements
and
their
uses.
It
provides
examples
of
each
kind
of
architecture
member
and
describes
the
special
command
statements
that
the
architecture
members
require.
It
also
provides
an
example
of
the
format
of
each
statement
and
lists
any
restrictions.
Chapter
12,
Managing
Complex
Projects,
describes
advanced
topics
that
aid
in
managing
complex
configurations.
Chapter
13,
SCLM
Support
for
DB2,
General
Information,
describes
how
to
configure
SCLM
and
DB2
to
work
together.
Chapter
14,
SCLM
Support
for
Workstation
Builds,
describes
how
to
set
up
and
use
SCLM
to
do
builds
on
the
workstation.
The
Glossary
of
SCLM
Terms
and
the
Index
sections
are
available
for
your
reference.
Using
LookAt
to
look
up
message
explanations
LookAt
is
an
online
facility
that
lets
you
look
up
explanations
for
most
of
the
IBM
messages
you
encounter,
as
well
as
for
some
system
abends
and
codes.
Using
LookAt
to
find
information
is
faster
than
a
conventional
search
because
in
most
cases
LookAt
goes
directly
to
the
message
explanation.
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
PCs,
Blazer,
or
Eudora
for
Palm
OS,
or
Opera
for
Linux
handheld
devices).
Link
to
the
LookAt
Mobile
Edition
from
the
LookAt
Web
site.
viii
z/OS
V1R6.0
ISPF
SCLM
Project
Managers
and
Developers
Guide
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.
Preface
ix
x
z/OS
V1R6.0
ISPF
SCLM
Project
Managers
and
Developers
Guide
Summary
of
Changes
z/OS
V1R6.0
ISPF
contains
the
following
changes
and
enhancements:
v
ISPF
Product
and
Library
changes
v
ISPF
Dialog
Manager
component
changes
(including
DTL
changes)
v
ISPF
Component
changes
v
ISPF
SCLM
Component
changes
v
ISPF
Client/Server
Component
changes
ISPF
Product
and
Library
changes
Changes
to
the
ZENVIR
variable.
Characters
1
through
8
contain
the
product
name
and
sequence
number,
in
the
format
ISPF
x.y,
where
x.y
indicates
the
version
number
and
release.
Note
that
the
x.y
value
is
not
necessarily
the
same
as
the
operating
system
version.
For
example,
a
value
of
ISPF
5.6
represents
ISPF
for
z/OS
Version
1
Release
6.0.
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.
ISPF
Dialog
Manager
component
changes
The
DM
component
of
ISPF
includes
the
following
new
functions
and
enhancements:
v
The
new
*REXX
panel
definition
statement
allows
the
inclusion
of
Rexx
code
within
a
panels
)INIT,
)REINIT,
or
)PROC
sections
to
perform
arithmetic,
verification,
transformation,
translation,
and
formatting
of
dialog
variables.
v
Enhancements
to
ISPF
File
Tailoring:
Added
support
for
continuation
of
control
statements.
Increased
maximum
imbed
levels
from
3
to
15.
Increased
maximum
select
levels
from
8
to
32.
Increased
the
maximum
number
of
parameters
on
a
control
statement
from
31
to
63.
Eliminated
exclusive
SPFEDIT
enqueue
on
a
skeleton
member
when
processing
a
skeleton.
Improved
skeleton
processing
by
reading
skeleton
records
into
storage.
Added
support
for
the
)DO
...
)ENDDO
control
statements.
Added
support
for
the
)IF
...
THEN
...
)ELSE
control
statements.
Added
)ITERATE
and
)LEAVE
control
words
for
use
within
)DO
...
)ENDDO
loops.
Added
the
)NOP
control
word,
which
can
be
used
with
a
null
)IF
or
)ELSE
statement.
Added
TBSCAN
support
to
the
)DOT
control
word.v
The
restriction
that
Language
Environment-enabled
programming
languages
can
not
be
used
for
ISPF
exits
has
been
partially
removed.
Exits
can
now
be
written
Copyright
IBM
Corp.
1990,
2004
xi
in
languages
that
use
the
LE
run-time
environment,
as
long
as
all
the
dialogs
and
service
routines
are
LE-conforming.
A
mixture
of
LE-conforming
main
dialog
code
and
service
routine
code
is
not
supported.
ISPF
Configuration
Utility
changes:
v
Added
support
for
zero
block
size
for
dynamic
allocation
of
the
ISPLIST,
ISPLOG,
ISPCTLx,
ISPLSTx,
and
ISPWRKx
data
sets.
v
Added
support
for
specifying
primary
and
secondary
space
for
the
ISPCTL0
and
ISPLSTx
data
sets.
v
New
keywords
control
what
happens
when
an
explicit
member
list
request
is
made
for
an
empty
PDS/E:
DISPLAY_EMPTY_MEMBER_LIST
DISPLAY_EMPTY_MEMBER_LIST_PATTERN
DISPLAY_EMPTY_MEMBER_LIST_FUNCTION
RESET_EMPTY_MEMBER_LIST_OPTIONS
Dialog
Tag
Language
(DTL)
changes
There
are
no
changes
to
Dialog
Tag
Language
(DTL)
for
this
release.
ISPF
Component
changes
The
ISPF
component
contains
the
following
new
functions
and
enhancements:
v
The
TBQUERY
service
has
been
enhanced
to
return
information
about
TBSORT
and
the
last
TBSARG
issued
against
a
table.
v
The
new
QTABOPEN
service
allows
an
ISPF
dialog
to
obtain
a
list
of
currently
open
ISPF
tables.
The
TBSTATS
or
TBQUERY
service
can
then
be
used
to
obtain
more
detailed
information
about
each
table.
v
A
new
Edit
primary
command,
COLS,
displays
a
non-scrolling
columns
line
in
Edit
or
View.
v
A
new
Edit
primary
command
and
edit
macro
command,
HIDE,
removes
the
excluded
lines
messages
from
the
display.
RESET
HIDE
restores
the
excluded
lines
messages.
v
The
CUT
Edit
primary
command
and
edit
macro
commands
now
support
two
new
flags:
X
specifies
to
cut
only
excluded
lines
to
the
clipboard.
NX
specifies
to
cut
only
nonexcluded
lines.
v
The
MODEL
edit
macro
command
now
issues
RC=4
if
the
model
exceeds
the
right
hand
margin
of
the
data
being
edited.
v
The
VOLUME
edit
macro
command
is
changed
to
permit
return
of
the
volume
serial
where
the
original
data
set
is
stored.
v
The
CURSOR
edit
assignment
statement
has
been
changed
as
follows:
if
the
cursor
is
in
the
command
area,
the
cursor
value
is
column
0
of
the
first
data
line
on
the
panel.
v
When
saving
a
member
list
to
a
dataset
using
the
SAVE
primary
command,
the
new
keyword
LONG
formats
all
dates
in
yyyy/mm/dd
format
for
the
member.
v
Documentation
has
been
added
for
the
OVOLUME
parameter
on
the
LMQUERY
service.
ISPF
SCLM
Component
changes
The
ISPF
SCLM
component
contains
the
following
new
functions
and
enhancements:
xii
z/OS
V1R6.0
ISPF
SCLM
Project
Managers
and
Developers
Guide
v
For
each
of
the
FLMCMD
services
a
new
panel
has
been
added,
providing
the
ability
to
select
a
service
from
a
menu
and
then
enter
the
service
parameters
in
an
ISPF
interface
panel.
These
panels
can
also
be
called
directly,
by
entering
the
FLMCMD
service
command
without
parameters.
v
The
new
Unit
of
Work
utility
allows
you
to
use
an
ARCHDEF
member
as
a
member
list
from
which
you
can
use
the
standard
SCLM
functions
such
as
select,
edit,
build,
view
build
map,
and
promote.
You
can
add
your
own
customized
line
commands
to
work
with
the
Unit
of
Work
member
List.
v
The
new
SCLM
Explorer
utility
provides
the
ability
to
select
any
architecture
definition
or
part
member
and
then
navigate
up
or
down
the
hierarchy
of
related
ARCHDEFs
or
parts.
ISPF
Client/Server
Component
changes
The
ISPF
Client/Server
Component
enables
a
panel
to
be
displayed
unchanged
(except
for
panels
with
graphic
areas)
at
a
workstation
using
the
native
display
function
of
the
operating
system
of
the
workstation.
ISPF
documents
call
this
running
in
GUI
mode.
There
are
no
changes
to
the
ISPF
Client/Server
for
this
release.
ISPF
Migration
Considerations
If
you
are
migrating
to
z/OS
V1R6.0
from
an
earlier
release
of
z/OS
or
from
OS/390
V2R10.0,
no
migration
actions
are
needed.
If
you
are
migrating
to
z/OS
V1R6.0
from
an
earlier
release
of
OS/390,
follow
the
migration
actions
for
OS/390
V2R10.0.
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
bookfor
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.
Summary
of
Changes
xiii
xiv
z/OS
V1R6.0
ISPF
SCLM
Project
Managers
and
Developers
Guide
Migrating
from
Previous
Versions
of
SCLM
When
migrating
from
one
release
of
ISPF
to
another,
you
must
reassemble
and
re-link
all
of
your
SCLM
Project
Definitions
using
the
macros
provided
with
the
new
release.
If
you
have
modified
any
of
the
SCLM-provided
macros
then
you
must
reintegrate
those
changes
with
the
new
SCLM-provided
macros
(see
Step
9:
Assemble
and
Link
the
Project
Definition
on
page
40).
Failure
to
do
this
results
in
unpredictable
results
during
SCLM
execution.
FLMCPYLB
Statements
Required
for
IOTYPE=A
In
z/OS
V1R2.0
ISPF
and
later,
SCLM
project
definitions
must
have
an
FLMCPYLB
statement
identifying
a
data
set
name
for
every
FLMALLOC
statement
with
IOTYPE=A
or
MALLOC=Y.
Project
and
language
definitions
with
missing
statements
(including
sample
languages
and
the
sample
project
included
in
prior
releases)
will
receive
an
assembly
error,
which
will
be
MNOTEs
following
the
FLMAEND
statement.
If
this
error
is
detected
when
a
project
definition
is
assembled,
you
can
correct
it
using
one
of
the
following:
v
Add
the
missing
FLMCPYLB
statements
with
an
appropriate
data
set
name
(or
specify
NULLFILE)
v
Change
the
IOTYPE
on
the
FLMALLOC
to
an
appropriate
value
for
the
translator
being
used
Versioning
Data
Sets
In
OS/390
V2R10
ISPF
and
later,
you
can
version
fixed
and
variable
outputs
as
well
as
editable
data.
If
your
project
contains
any
record
format
U
data,
including
load
modules,
then
you
will
need
to
review
the
FLMATVER
macros
in
your
project
definition.
An
asterisk
(*)
value
for
the
TYPE
(TYPE=*)
on
an
FLMATVER
macro
with
versioning
enabled
(VERSION=YES)
will
cause
an
error
message
to
be
issued
when
SCLM
attempts
to
version
the
record
format
U
data
found
in
the
project.
Under
those
circumstances,
FLMATVER
macros
should
be
added
to
specify
each
type
to
be
versioned
when
the
project
contains
record
format
U
data.
This
change
is
not
necessary
when
auditing
only
is
enabled
(VERSION=NO).
Additional
versioning
data
sets
must
be
allocated
for
any
new
types
that
you
might
now
want
to
version.
Year
2000
Support
With
the
release
of
OS/390
Version
1
Release
3.0,
SCLM
began
supporting
dates
beyond
the
year
2000.
This
has
caused
a
change
to
the
format
of
date
fields
stored
in
the
SCLM
VSAM
databases.
After
you
have
used
this
release
with
a
system
date
after
December
31,
1999,
you
cannot
go
back
to
an
earlier
release
of
SCLM
unless
it
also
has
support
for
dates
beyond
the
year
2000.
The
internal
date
format
used
by
SCLM
has
also
changed.
The
length
and
format
of
the
$acct_info
and
$list_info
date
fields
returned
by
SCLM
services
are
different.
These
fields
are
now
8
characters
long
and
have
the
format
YYYYMMDD
(year,
month,
day).
In
addition,
the
1character
alignment
field
in
the
$acct_info
structure
is
now
three
characters
long.
Any
user-written
programs
that
use
the
SCLM
service
interface
must
be
modified
accordingly.
Copyright
IBM
Corp.
1990,
2004
xv
Load
Module
Accounting
Records
and
SSI
Information
In
ISPF
Version
4.2
without
APAR
OW18306,
when
load
modules
without
an
SSI
area
(load
modules
that
were
linked
without
the
SETSSI
option)
were
migrated
into
SCLM,
or
when
load
modules
were
built
using
an
architecture
definition
that
did
not
include
the
LOAD
keyword,
the
dates
and
times
in
the
accounting
records
for
the
load
modules
were
set
to
zeros
or
random
characters.
Starting
with
OS/390
V1R3.0,
or
with
ISPF
Version
4.2
with
APAR
OW18306,
it
is
not
necessary
to
build
a
load
module
with
the
SETSSI
option
in
order
to
migrate
it
into
SCLM
and
still
have
correct
accounting
and
SSI
information.
The
SCLM
MIGRATE
operation
generates
the
data
for
the
SSI
area
and
updates
the
accounting
record
with
the
correct
dates
and
times.
Similarly,
SCLM
BUILD
generates
the
SSI
information
and
sets
the
correct
dates
and
times
in
the
accounting
records
for
load
modules
that
are
generated
without
an
LEC
architecture
definition.
If
you
are
migrating
from
a
system
with
ISPF
Version
4.2
without
APAR
OW18306
or
earlier
release,
take
these
actions:
v
If
you
have
previously
migrated
load
modules
into
SCLM
that
did
not
have
the
SSI
information
set,
then
you
should
migrate
these
modules
into
SCLM
again.
Migrating
these
members
again
ensures
that
the
SSI
information
is
set
and
that
the
accounting
dates
and
times
are
correct.
v
If
you
have
previously
generated
load
modules
in
SCLM
without
an
LEC
architecture
definition
(meaning
that
the
accounting
record
date
and
time
fields
are
zeros
or
random
characters)
then
these
modules
are
rebuilt
the
first
time
a
build
is
performed
after
installing
z/OS
V1R6.0
ISPF.
This
rebuild
is
necessary
to
ensure
that
the
SSI
and
accounting
record
information
for
the
load
modules
are
synchronized
and
have
been
updated
with
valid
data.
You
might
want
to
schedule
the
first
build
of
your
projects
with
the
affected
load
modules
at
a
time
that
minimizes
the
impact
to
your
system.
xvi
z/OS
V1R6.0
ISPF
SCLM
Project
Managers
and
Developers
Guide
Whats
in
the
z/OS
V1R6.0
ISPF
library?
You
can
order
the
ISPF
books
using
the
numbers
provided
below.
z/OS
V1R6.0
ISPF
Title
Order
Number
z/OS
V1R6.0
ISPF
Dialog
Tag
Language
Guide
and
Reference
SC34-482403
z/OS
V1R6.0
ISPF
Planning
and
Customizing
GC34-481403
z/OS
V1R6.0
ISPF
Users
Guide
Volume
I
SC34-482203
z/OS
V1R6.0
ISPF
Users
Guide
Volume
II
SC34-482303
z/OS
V1R6.0
ISPF
Services
Guide
SC34-481903
z/OS
V1R6.0
ISPF
Dialog
Developers
Guide
and
Reference
SC34-482103
z/OS
V1R6.0
ISPF
Reference
Summary
SC34-481603
z/OS
V1R6.0
ISPF
Edit
and
Edit
Macros
SC34-482003
z/OS
V1R6.0
ISPF
Messages
and
Codes
SC34-481503
z/OS
V1R6.0
ISPF
Software
Configuration
and
Library
Manager
Project
Managers
and
Developers
Guide
SC34-481703
z/OS
V1R6.0
ISPF
Software
Configuration
and
Library
Manager
Reference
SC34-481803
Copyright
IBM
Corp.
1990,
2004
xvii
xviii
z/OS
V1R6.0
ISPF
SCLM
Project
Managers
and
Developers
Guide
The
ISPF
User
Interface
ISPF
provides
an
action
bar-driven
interface
that
exploits
many
of
the
usability
features
of
Common
User
Access
(CUA)
interfaces.
Refer
to
Object-Oriented
Interface
Design:
IBM
Common
User
Access
Guidelines
for
additional
information.
These
action
bars
give
you
another
way
to
move
around
in
ISPF,
as
well
as
the
ability
to
nest
commands.
Command
nesting
allows
you
to
suspend
an
activity
while
you
perform
a
new
one
rather
than
having
to
end
a
function
to
perform
another
function.
This
chapter
primarily
explains
the
action
bar-driven
interface
and
the
use
of
ISPFs
graphical
user
interface
(GUI).
Some
Terms
You
Should
Know
The
following
terms
are
used
in
this
document:
action
bar
The
area
at
the
top
of
an
ISPF
panel
that
contains
choices
that
give
you
access
to
actions
available
on
that
panel.
When
you
select
an
action
bar
choice,
ISPF
displays
a
pull-down
menu.
function
key
In
previous
releases
of
ISPF,
a
programmed
function
(PF)
key.
This
is
a
change
in
terminology
only.
mnemonics
Action
bar
choices
can
be
defined
with
a
underscored
letter
in
the
action
bar
choice
text.
In
host
mode
you
can
access
the
action
bar
choice
with
the
ACTIONS
command
and
parameter
x,
where
x
is
the
underscored
letter
in
the
action
bar
choice
text.
In
GUI
mode
you
can
use
a
hot
key
to
access
a
choice
on
the
action
bar;
that
is,
you
can
press
the
ALT
key
in
combination
with
the
letter
that
is
underscored
in
the
action
bar
choice
text.
modal
pop-up
window
A
type
of
window
that
requires
you
to
interact
with
the
panel
in
the
pop-up
before
continuing.
This
includes
canceling
the
window
or
supplying
information
requested.
modeless
pop-up
window
A
type
of
window
that
allows
you
to
interact
with
the
dialog
that
produced
the
pop-up
before
interacting
with
the
pop-up
itself.
point-and-shoot
text
Text
on
a
screen
that
is
cursor-sensitive.
See
Point-and-Shoot
Text
Fields
on
page
xxiv
for
more
information.
pop-up
window
A
bordered
temporary
window
that
displays
over
another
panel.
pull-down
menu
A
list
of
numbered
choices
extending
from
the
selection
you
made
on
the
action
bar.
The
action
bar
selection
is
highlighted;
for
example,
Utilities
in
Figure
1
on
page
xxi
appears
highlighted
on
your
screen.
You
can
select
an
action
either
by
typing
in
its
number
and
pressing
Enter
or
by
selecting
the
action
with
your
cursor.
ISPF
displays
the
requested
panel.
If
your
choice
Copyright
IBM
Corp.
1990,
2004
xix
contains
an
ellipsis
(...),
ISPF
displays
a
pop-up
window.
When
you
exit
this
panel
or
pop-up,
ISPF
closes
the
pull-down
and
returns
you
to
the
panel
from
which
you
made
the
initial
action
bar
selection.
push
button
A
rectangle
with
text
inside.
Push
buttons
are
used
in
windows
for
actions
that
occur
immediately
when
the
push
button
is
selected
(available
only
when
you
are
running
ISPF
in
GUI
mode).
select
In
conjunction
with
point-and-shoot
text
fields
and
action
bar
choices,
this
means
moving
the
cursor
to
a
field
and
simulating
Enter.
How
to
Navigate
in
ISPF
Using
the
Action
Bar
Interface
Most
ISPF
panels
have
action
bars
at
the
top;
the
choices
appear
on
the
screen
in
white
by
default.
Many
panels
also
have
point-and-shoot
text
fields,
which
appear
in
turquoise
by
default.
The
panel
shown
in
Figure
3
on
page
xxii
has
both.
Action
Bars
Action
bars
give
you
another
way
to
move
through
ISPF.
If
the
cursor
is
located
somewhere
on
the
panel,
there
are
several
ways
to
move
it
to
the
action
bar:
v
Use
the
cursor
movement
keys
to
manually
place
the
cursor
on
an
action
bar
choice.
v
Type
ACTIONS
on
the
command
line
and
press
Enter
to
move
the
cursor
to
the
first
action
bar
choice.
v
Press
F10
(Actions)
or
the
Home
key
to
move
the
cursor
to
the
first
action
bar
choice.
If
mnemonics
are
defined
for
action
bar
choices,
you
can:
In
3270
mode,
on
the
command
line,
type
ACTIONS
and
the
mnemonic
letter
that
corresponds
to
an
underscored
letter
in
the
action
bar
choice
text.
This
results
in
the
display
of
the
pull-down
menu
for
that
action
bar
choice.
In
3270
mode,
on
the
command
line
enter
the
mnemonic
letter
that
corresponds
to
an
underscored
letter
in
the
action
bar
choice
text,
and
press
the
function
key
assigned
to
the
ACTIONS
command.
This
results
in
the
display
of
the
pull-down
menu
for
that
action
bar
choice.
In
GUI
mode,
you
can
use
a
hot
key
to
access
a
choice
on
an
action
bar
or
on
a
pull-down
menu;
that
is,
you
can
press
the
ALT
key
in
combination
with
the
mnemonic
letter
that
is
underscored
in
the
choice
text
to
activate
the
text.
Use
the
tab
key
to
move
the
cursor
among
the
action
bar
choices.
If
you
are
running
in
GUI
mode,
use
the
right
and
left
cursor
keys.
Notes:
1.
ISPF
does
not
provide
a
mouse
emulator
program.
This
document
uses
select
in
conjunction
with
point-and-shoot
text
fields
and
action
bar
choices
to
mean
moving
the
cursor
to
a
field
and
simulating
Enter.
2.
Some
users
program
their
mouse
emulators
as
follows:
v
Mouse
button
1
position
the
cursor
to
the
pointer
and
simulate
Enter
v
Mouse
button
2
simulate
F12
(Cancel).3.
If
you
want
the
Home
key
to
position
the
cursor
at
the
first
input
field
on
an
ISPF
panel,
type
SETTINGS
on
any
command
line
and
press
Enter
to
display
the
ISPF
Settings
panel.
Deselect
the
Tab
to
action
bar
choices
option.
4.
If
you
are
running
in
GUI
mode,
the
Home
key
takes
you
to
the
beginning
of
the
current
field.
The
ISPF
User
Interface
xx
z/OS
V1R6.0
ISPF
SCLM
Project
Managers
and
Developers
Guide
When
you
select
one
of
the
choices
on
the
action
bar,
ISPF
displays
a
pull-down
menu.
Figure
1
shows
the
pull-down
menu
displayed
when
you
select
Options
on
the
ISPF
Primary
Option
Menu
action
bar.
To
select
a
choice
from
the
Options
pull-down
menu,
type
its
number
in
the
entry
field
(underlined)
and
press
Enter
or
select
the
choice.
To
cancel
a
pull-down
menu
without
making
a
selection,
press
F12
(Cancel).
For
example,
if
you
select
choice
6,
ISPF
displays
the
Dialog
Test
Application
ID
pop-up,
as
shown
in
Figure
2
on
page
xxii.
Note:
If
you
entered
a
command
on
the
command
line
prior
to
selecting
an
action
bar
choice,
the
command
is
processed,
and
the
pull-down
menu
is
never
displayed.
The
CANCEL,
END,
and
RETURN
commands
are
exceptions.
These
three
commands
are
not
processed
and
the
cursor
is
repositioned
to
the
first
input
field
in
the
panel
body.
If
there
is
no
input
field,
the
cursor
is
repositioned
under
the
action
bar
area.
If
you
are
running
in
GUI
mode
and
select
an
action
bar
choice,
any
existing
command
on
the
command
line
is
ignored.
Menu
Utilities
Compilers
1Options
Status
Help
1.
General
Settings
2.
CUA
Attributes...
0
Settings
Terminal
a
3.
Keylists...
ID
.
:
MBURNS
1
View
Display
so
4.
Point-and-Shoot...
.
.
.
:
11:19
2
Edit
Create
or
5.
Colors...
inal.
:
3278
3
Utilities
Perform
ut
6.
Dialog
Test
appl
ID...
en.
.
:
1
4
Foreground
Interactiv
uage.
:
ENGLISH
5
Batch
Submit
job
for
language
processing
Appl
ID
.
:
ISR
6
Command
Enter
TSO
or
Workstation
commands
TSO
logon
:
ISPF
7
Dialog
Test
Perform
dialog
testing
TSO
prefix:
MBURNS
9
IBM
Products
IBM
program
development
products
System
ID
:
ISD1
10
SCLM
SW
Configuration
Library
Manager
MVS
acct.
:
IBMGSA
11
Workplace
ISPF
Object/Action
Workplace
Release
.
:
ISPF
5.5
Enter
X
to
Terminate
using
Log/List
defaults
Option
===>
F1=Help
F2=Split
F3=Exit
F7=Backward
F8=Forward
F9=Swap
F10=Actions
F12=Cancel
1
The
selected
action
bar
choice
is
highlighted.
Figure
1.
Panel
with
an
Action
Bar
Pull-Down
Menu
The
ISPF
User
Interface
The
ISPF
User
Interface
xxi
Command
Nesting
You
can
use
the
action
bars
to
suspend
an
activity
while
you
perform
a
new
one.
For
example,
if
you
are
editing
a
data
set
and
want
to
allocate
another
data
set,
select
the
Data
set
choice
from
the
Utilities
pull-down
on
the
Edit
panel
action
bar.
Menu
Utilities
Compilers
Options
Status
Help
Dialog
Test
Application
ID
ption
Menu
0
Change
the
application
ID
for
ters
User
ID
.
:
MBURNS
1
Dialog
Test.
istings
Time.
.
.
:
11:19
2
data
Terminal.
:
3278
3
Application
ID
.
.
ISR
s
Screen.
.
:
1
4
cessing
Language.
:
ENGLISH
5
processing
Appl
ID
.
:
ISR
6
Command
===>
commands
TSO
logon
:
ISPF
7
F1=Help
F2=Split
F3=Exit
TSO
prefix:
MBURNS
9
F9=Swap
F12=Cancel
products
System
ID
:
ISD1
1
Manager
MVS
acct.
:
IBMGSA
11
Workplace
ISPF
Object/Action
Workplace
Release
.
:
ISPF
5.5
Enter
X
to
Terminate
using
Log/List
defaults
Option
===>
F1=Help
F2=Split
F3=Exit
F7=Backward
F8=Forward
F9=Swap
F10=Actions
F12=Cancel
Figure
2.
Pop-Up
Selected
from
an
Action
Bar
Pull-Down
1
Menu
Utilities
Compilers
Options
Status
Help
ISPF
Primary
Option
Menu
2
3
0
Settings
Terminal
and
user
parameters
User
ID
.
:
MBURNS
1
View
Display
source
data
or
listings
Time.
.
.
:
12:29
2
Edit
Create
or
change
source
data
Terminal.
:
3278
3
Utilities
Perform
utility
functions
Screen.
.
:
1
4
Foreground
Interactive
language
processing
Language.
:
ENGLISH
5
Batch
Submit
job
for
language
processing
Appl
ID
.
:
ISR
6
Command
Enter
TSO
or
Workstation
commands
TSO
logon
:
ISPF
7
Dialog
Test
Perform
dialog
testing
TSO
prefix:
MBURNS
9
IBM
Products
IBM
program
development
products
System
ID
:
ISD1
10
SCLM
SW
Configuration
Library
Manager
MVS
acct.
:
IBMGSA
11
Workplace
ISPF
Object/Action
Workplace
Release
.
:
ISPF
5.5
Enter