z/OS V1.

13 Sysprog Goody Bag

Greg Daynes
[email protected]
IBM z/OS Installation and Deployment Architect

March 15, 2012

Session 10645

© 2012 IBM Corporation

Acknowledgement

Most of the material in the presentation came from:

 Bob Rogers - IBM Systems z Distinguished Engineer and System z
Philosopher

Bob Me

–Unfortunately, Bob couldn’t attend SHARE this week

–More unfortunately (for me) he asked me to present in his place
• I don’t have Bob’s knowledge, anecdotes, or sense of humor
• Therefore, I’ve added more content and actual experience using most of the
functions

 Roger Fowler – Consulting IT Specialist

2 © 2012 IBM Corporation

Acknowledgement

 Roger and Bob blatantly “stole” their material from various z/OS
development teams
 Minimally this list includes:
–ISPF – Peter Van Dyke
–JES2 – Tom Wasik
–JES3 – Peter Kania
–DFSMS – Wayne Rhoten, Rohan Kurane, Tan Q Nguyen, Stephen M
Branch, Patrick P. Dempsey, Jerry Dearing, Diego Medina, Jon Lynds,
Jerry Codde
–SMF – Anthony Sofia
–HCD – Friedrich Beichter
–IOS - Ilene Goldman

3 © 2012 IBM Corporation

 z/OS V1.13 Enhancements
ISPF
–Miscellaneous enhancements
JES2
–“Batch Modernization” enhancements
–Spool dataset enhancements
JES3
–JES3 Dynamic Spool Addition
DFSMS
–Catalog enhancements
–PDSE enhancements
–Miscellaneous enhancements
SMF
–SMF logstream enhancements
HCD
–New warning messages
IOS
–Improved Channel Recovery
4
z/OSMF © 2012 IBM Corporation
 ISPF V1.13 Enhancements
ISPF Dataset allocate support in DSList
ISPF Support for managing z/OS Unix ACLs
ISPF Support for displaying PDS member
extended statistics
ISPF Editor Support for Line Command Macros

5 © 2012 IBM Corporation

ISPF Dataset allocate support in DSList
 New AL line command in ISPF Dataset List utility (ISPF 3.4)
–Name of new dataset must follow – either quoted or unquoted

 When AL entered against an existing dataset, panel displayed with

options
–Create dataset using attributes of existing dataset
–Specify the attributes on the Allocate New Dataset panel

 When AL entered against an deleted dataset,

–No dataset name needs to be specified against a deleted dataset entry
–Panel displayed to specify the attributes on the Allocate New Dataset
panel

6 © 2012 IBM Corporation

ISPF Dataset allocate support in DSList
 Using AL against an existing dataset:

7 © 2012 IBM Corporation

ISPF Dataset allocate support in DSList

8 © 2012 IBM Corporation

ISPF Dataset allocate support in DSList
 Using AL against a deleted dataset:

9 © 2012 IBM Corporation

ISPF Dataset allocate support in DSList

10 © 2012 IBM Corporation

ISPF Support for managing z/OS Unix ACLs
 Adding ACL support is part of the long term plan for the z/OS UNIX
Directory List Utility (ISPF option 3.17) to provide most of the
functions currently support by the ISHELL utility

 Reduce the need for users to switch between the z/OS UNIX
Directory List Utility and ISHELL

 Introduces a new z/OS UNIX Directory List Utility line command that
invokes a dialog where the ACLs for a file can be managed

 No need to leave the z/OS UNIX Directory List Utility when you need
to see or update ACLs for a file

11 © 2012 IBM Corporation

ISPF Support for managing z/OS Unix ACLs
 The z/OS UNIX Directory List Utility (ISPF option 3.17) now supports the
new MA line command for the display and update of ACLs for a file:

– The MA line command can be entered against any file or directory in

the list

– When the MA line command is entered the z/OS UNIX ACL List panel
is displayed showing a list of any ACL entries defined for the file

– The z/OS UNIX ACL List panel supports the following primary
commands:
Command Function
A Add a new ACL
SA sort the ACL list alphabetically by userid
SN sort the ACL list numerically on UID
ST sort the ACL list alphabetically by type

12 © 2012 IBM Corporation

ISPF Support for managing z/OS Unix ACLs
 Each ACL entry on the z/OS UNIX ACL List panel has the following
fields:
Field Description
S Input field for entering a line command against an ACL entry

UID The z/OS user or group ID value (numeric)

Read Indicates whether the user or group has the authority to read the
file

Write Indicates whether the user or group has the authority to write to
the file

Execute Indicates whether the user or group has the authority to execute
the file

Name The name associated with the UID value

Type Indicates whether the ACL entry is for a user or group

13 © 2012 IBM Corporation

ISPF Support for managing z/OS Unix ACLs

14 © 2012 IBM Corporation

ISPF Support for managing z/OS Unix ACLs
 The following line commands can be entered in the S field for an ACL
entry:

Command Description

A Add a new ACL entry

D Delete the ACL entry
X List the members for the group defined in the ACL entry

15 © 2012 IBM Corporation

ISPF Support for managing z/OS Unix ACLs
 Adding a new ACL entry

16 © 2012 IBM Corporation

ISPF Support for managing z/OS Unix ACLs
 Adding a new ACL entry

17 © 2012 IBM Corporation

ISPF Support for managing z/OS Unix ACLs
 Deleting a new ACL entry

18 © 2012 IBM Corporation

ISPF Support for managing z/OS Unix ACLs
 Displaying the list of members in a group

19 © 2012 IBM Corporation

ISPF Support for displaying PDS member
extended statistics
 In z/OS V1R11 the ISPF statistics maintained for PDS members were
extended to support line count values greater than 65535

 ISPF services were enhanced to return these extended line count

values however no function was provided to display these values

 The ISPF enhanced member list now supports the new I line
command to display panel ISRUDSI showing the ISPF statistics for a
member
–The enhanced member list is displayed using the M, B, E, or V line
commands in the Data Set List display (ISPF option 3.4)
–The I line command can be used against any member in a partitioned
data set
• It is not restricted to members that have extended line count statistics
defined
20 © 2012 IBM Corporation
ISPF Support for displaying PDS member extended
statistics

21 © 2012 IBM Corporation

ISPF Support for displaying PDS member
extended statistics
 DFSMS stores the job name and step name that created a data set in
the format-9 DSCB
• For datasets stored in the cylinder-managed area of an EAV
• No easy way of displaying this information

 ISPF Dataset information panels now display this information

 Information also stored into new ISPF variables for easy access by
dialogs

22 © 2012 IBM Corporation

ISPF Support for displaying PDS member
extended statistics
 Data Set Information panels show the creation job and step names
when available from the format-9 DSCB

23 © 2012 IBM Corporation

ISPF Support for displaying PDS member
extended statistics
 The DSINFO service returns the creation job and step names in the
following variables:

ZDSCJOBN - creation job name

ZDSCSTPN - creation step name

 The LMDLIST service returns the creation job and step names in the
following variables:

ZDLCJOBN - creation job name

ZDLCSTPN - creation step name

24 © 2012 IBM Corporation

ISPF Editor Support for Line Command Macros
 Integrate the support added by LMAC into the editor

 Supports user-written line command macros

 No need to download and install LMAC tool

25 © 2012 IBM Corporation

ISPF Editor Support for Line Command macros
■ User defined line commands and the edit macros they invoke are
defined in an ISPF table
■ The ISPF Table Utility (ISPF option 3.16) is modified to assist with
defining the user line command table
■ New line command table input field is added to the edit and view
entry panels
–When the line command table is specified the line commands specified
in the table are able to be used during the edit session
■ The EDIT and VIEW services also allow a line command table to be
passed by the caller

26 © 2012 IBM Corporation

ISPF Editor Support for Line Command macros

 Option added to the ISPF Table Utility (ISPF option 3.16) entry panel
to help users create and edit line command tables:

27 © 2012 IBM Corporation

ISPF Editor Support for Line Command macros

■ Special format of the table edit panel displayed showing columns

specific to a user edit line command table:

28 © 2012 IBM Corporation

ISPF Editor Support for Line Command macros

29 © 2012 IBM Corporation

ISPF Editor Support for Line Command macros

Specify a user line command table on the edit or view entry panel to
enable user line commands for the edit session:

30 © 2012 IBM Corporation

ISPF Editor Support for Line Command macros

Using the CE, RV, LEF, and RIT line commands from the sample user
line command macro:

31 © 2012 IBM Corporation

 JES2 V1.13 Enhancements
Batch Modernization
–JES2 Instream data in PROCs and INCLUDE members
–JES2 Job Return Code
–JES2 Requeue job by command on a step boundary
–JES2 Spin any
Spool Enhancements
–JES2 Extend Spool dataset
–JES2 Spool dataset name
–JES2 Spool volume prefix
–JES2 Spool migration
32 © 2012 IBM Corporation
JES2 Instream Data in PROCs and INCLUDE members

 Previously, instream data was not allowed in JCL PROCs or

INCLUDEs
 Support now added to allow instream data sets to be created when
processing DD DATA or DD * JCL within PROCs or INCLUDEs
–Support added for both cataloged and instream procedures
–Control data sets do not have to be separate from PROCs or INCLUDEs
– Works like instream data in normal JCL stream
 Support is based on where the job converts (z/OS 1.13)
–Can run on downlevel system
 Instream data sets in PROCs…
–Are included in viewing original JCL via SDSF (SJ command)
–Are included in extended status DSLIST function (SDSF ?)
–Are NOT included in SPOOL Data Set Browse of JCL
–Are NOT transmitted to other nodes or offloaded
 New SYSIN data sets are included in extended status DSLIST function
 Works for batch jobs as well as started tasks
33 © 2012 IBM Corporation
JES2 Instream Data in PROCs and INCLUDE members

Embedding instream data in a JES2 procedure:

//HELLO PROC
//STEPA EXEC PGM=IEBGENER
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT=*
//SYSUT2 DD SYSOUT=*
//SYSUT1 DD *
HELLO WORLD
// PEND

34 © 2012 IBM Corporation

JES2 Instream Data in PROCs and INCLUDE members

 SDSF - SJ

 IEBGENER Output

35 © 2012 IBM Corporation

JES2 Job Return Code
Previously, no easy way of determining success or
failure of a job
New job return code to report on outcome of entire job
New JOBRC keyword on JOB card
–Possible values for JOBRC keyword
• MAXRC – Default, job return code is the max of any step
• LASTRC – Job return code is the return code of the last step
• (STEP,stepname.procstepname) – Job return code is indicated step
if it executes, otherwise reverts to MAXRC

JOBCLASS JOBRC= MAXRC|LASTRC to affect

processing for all jobs in the job class
–JOBRC keyword on job card takes precedence
36 © 2012 IBM Corporation
JES2 Job Return Code

Updated HASP165 message text

–Jobname ENDED AT node reason
– Examples of reason:
• MAXCC=code - JOBRC was not specified
 Code is now always 4 digits (MAXCC=0000)
• JOBRC=code - JOBRC was specified and affected the return code
• MAXRC=code - JOBRC was specified but MAXRC was returned
• ABENDED Sxxx,Uyyy
• ABENDED abend_code, JOBRC=code
 JOBRC=(STEP,stepname), step executed, but later step ABENDed

37 © 2012 IBM Corporation

JES2 Requeue Job by Command on a Step Boundary

Previously, no easy way to get a job out of execution

before job end
Now have a new operand on the $EJ command that
forces a job out of execution when the current step ends
–Optional HOLD operand makes job held
–Job is requeued for execution
New JES2 command option
– $EJxxxx,STEP[,HOLD]
• Full cross member support
Utilizes existing restart logic (continue restart) to
perform function
– Requires JES journal to be active
• JOBCLASS(x) JOURNAL=YES
38 © 2012 IBM Corporation
JES2 Spin Any
 Previously, JESLOG spin only deals with job logs and system
message data sets
– Other spin data sets may exist that couldn’t be spun
 JES2 now provides the ability to ‘spin’ any SPIN SPOOL datasets
– Can free SPOOL space associated with log data sets created by long
running jobs
 Update to SPIN= DD operand specification in JCL
–Similar in function to JESLOG= keyword on job card
• SPIN=(UNALLOC,option) where option is one of:
o ‘hh:mm’ – Spin data set at specified time
o +hh:mm’ – Spin data set at interval specified
o nnn [K|M] – Spin every nnn records
o NOCMD – Cannot spin data set by command (current processing)
o CMDONLY – Spin only when a command is issued (default)

 Also supported in dynamic allocation and TSO ALLOC

 $TJn,SPIN,DDNAME=ddname – command can spin data set on
demand
–If you omit DDNAME= all active SPIN data sets will be spun
39 © 2012 IBM Corporation
JES2 Extend Spool dataset
 Can now dynamically extend (expand) a SPOOL data set to adjacent free
space on the device after the current SPOOL data set.
 Operator requests the extend via command
– Can ask for maximum available size or specific, larger size
– DFSMS services used to extend the data set into adjacent free space
– JES2 updates SPOOL volume size information based on new extent size
– Extend can occur without impacting running jobs
 Command to extend SPOOL to adjacent free space.
– $TSPOOL(xxxxxx),SPACE=
• The syntax of the SPACE parameter is same as the $S SPOOL command.
o MAX, (TRK,xxxx), (CYL,xxxx)
• SPACE= specifies the new TOTAL size of the SPOOL data set (not an increment).
 The extend can occur while the SPOOL volume is active and does not impact
any running address spaces.
– JES2 will format the new space added to the volume.
 Extend occurs without impacting running jobs
– New space is always formatted by JES2
 New message $HASP740 indicates Extend is successful
40 © 2012 IBM Corporation
JES2 Extend Spool dataset
 Extension of the data set is limited by:
– SPOOL volume must be STATUS=ACTIVE with no commands or migration
active or pending against it, and using relative addressing
– Singe JES2 SPOOL extent per volume restriction still applies
– Available free space contiguous (after) to the JES2 SPOOL extent
– Total size limited to architecture
• JES2 limit is based on LARGEDS on SPOOLDEF
o Allowed/Always – limit is 1M tracks
o Fail – limit is 64K
• DSCB format limits expansion into EAS storage
o Should migrate to CYL_MANAGED=ALLOWED
o Allocate SPOOL using DD EATTR = OPT to build format 8/9 DSCB
– All members of the MAS must be at JES2 z/OS V1.13
• Down level members can later join the MAS and use the extended data set
 $DSPOOL displays the results of the extend
– $DSPOOL,TGNUM to display the number of track groups in the data set after
the extend
– $DSPL,UNITDATA to display the track range (TRKRANGE) of the data set
after the extend

41 © 2012 IBM Corporation

JES2 Spool Data Set Name
 Previously, JES2 used the same spool dataset name on all spool
volumes
 SPOOL data set name can now be specified on:
– Start SPOOL command for a new volume: $SSPOOL(x),DSN=
– New SPOOL Initialization statement: SPOOL(x) DSName=
 SPOOLDEF DSNAME= is the default name used
 SPOOLDEF DSNMASK= limits possible data set names
–DSNMASK= can contain generics
–Supplied SPOOL data set names must match the mask
–If not specified, DSNAME= must match SPOOLDEF DSNAME=
 Use of a non-standard DSNAME= requires z11 $ACTIVATE mode
– Cannot activate to z2 mode if non-standard DSNAME used

42 © 2012 IBM Corporation

JES2 Spool Volume Prefix
 Previously, JES2 spool volume prefix was too restrictive
 The SPOOLDEF VOLUME= keyword has been enhanced to support
generics.
– Still limited to 5 characters
– The value for VOLUME= can be altered by a $T SPOOLDEF command
– Only used when volume is started
 If no generics, then prefix
– Acts like it does in prior releases
 If generics in value, then starting SPOOL VOLSER must match pattern
specified
– For example SPOOLDEF VOLUME=SPL*
 Should not use until all members migrated to z/OS 1.13
– If VOLUME= contains generics, you cannot start a pre z/OS 1.13 JES2 into the
MAS.
– However, if you $T SPOOLDEF VOLUME= to non-generics down level members
can again join the MAS.
• The existing SPOOL volumes will continue to be used (even though they do
not match the prefix).
43 © 2012 IBM Corporation
JES2 Spool Migration

Currently no quick and easy way of removing a spool

volume without impacting active systems or subsystems
JES2 now supports a spool migration command
–Automates the migration process.
–Existing active SPOOL pointers (MTTRs and MQTRs) are
unaffected.
–SPOOL volume consolidation
–JES2 services will make the migration transparent
Warning: If you have applications that access SPOOL
directly, you will break!

44 © 2012 IBM Corporation

JES2 Spool Migration
 z/OS 1.13 SPOOL migration function is being enabled
–APAR OA36158 closed February 24, 2012
• PTF UA64366 closed yesterday (March 14, 2012)!!!
 URL for the new SPOOL Migration web page:
–http://www-03.ibm.com/systems/z/os/zos/jes2_spoolmigration.html
 $M SPOOL command to move data off volume
–Faster than $P SPOOL (Minutes not days)
 Command works with active address spaces using volume
–Less activity is better/faster but no need to IPL to stop active jobs
 Goal of SPOOL migration is to stop using SPOOL data set
–Old data set can be deleted and SPOOL volume taken offline
–It is NOT to eliminate the internal representation of the volume
 After a successful SPOOL migration
–$DSPOOL still shows volume
–$DJQ,SPOOL= still displays volume
45 –New status is MAPPED © 2012 IBM Corporation
JES2 Spool Migration
Some new terms
 Migrator :
–The member that coordinates the migration.
 Migration Phase :
–The current 'step' of the migration process.
 Source Volume :
–The SPOOL volume to be migrated.
 Target Volume :
–The SPOOL volume to receive the migrated data.
 MERGE Migration :
–Copy a Source Volume to free space on an existing Target Volume.
 MOVE Migration :
–Copy an inactive Source Volume to a new Target Volume.
46 © 2012 IBM Corporation
JES2 Spool Migration
More new terms
 Mapped Volume:
–When a Merge Migration completes, the Source Volume becomes
Mapped.
–Remains Mapped until all jobs and SYSOUT that have space on the
Source Volume have been purged.
–When Mapped, the source dataset can be removed and the physical
device can be removed.
 Mapped Target:
–A volume with at least one volume Merged onto it.
 Reserved :
–New SPOOL attribute.
–Indicates if the spool volume is selectable but not allocatable.
–Used to Reserve a new volume for future Merge Migration(s).
–Reserved volumes have no entries in the BLOB.
47 © 2012 IBM Corporation
JES2 Spool Migration
 Phases of a SPOOL migration
–PENDING – Command issued and queued for processing
–INITIALIZING – Create data structures and subtasks.
–SETUP – Prepare source and target data set
–COPY – First pass copy of all data from source to target
–CATCHUP – Second pass copy of tracks updated by active
applications
–CANCEL – Error phase that synchronizes stopping migration
–BACKOUT – Error phase to undo any work done in migration
–CLEANUP – Delete data structures and end active migration
 Cancel can be requested up until start of catchup phase
–Internal cancel can occur later in error recovery cases
 Phase start/end messages issued to SYSLOG
–DEBUG VERBOSE=YES sends messages to console
 Some source volume state changes occur before the INITIALIZING
phase and after the CLEANUP phase
48 © 2012 IBM Corporation
JES2 Spool Migration
 Two forms of SPOOL migration, MOVE and MERGE
–Move takes all data on an existing volume and moves it to a new one
• Source must be INACTIVE ($Z SPOOL done)
o No active jobs on the volume
• Target cannot be currently an active SPOOL volume
• Can specify space to use to create data set on target
• At the end of move, old (source) volume does not exist
• Target after a move is active
–Merge takes all data on one volume and merges it onto free space on
another volume
• Most flexible migration option
• Source can be in any state with active jobs/address spaces
o Less activity is good
• Results is a mapped volume that goes away when all jobs using it are
deleted
o Similar to $P SPOOL but device is no longer in use

49 © 2012 IBM Corporation

JES2 Spool Migration
Merge migration
 Copies an existing Source volume to free space on a Target volume
 Upon completion, the Source Volume becomes a Mapped Volume.
–Remains MAPPED until all jobs and SYSOUT that have space on the
Source Volume are purged. It then goes away (no longer exists).

Pre-merge configuration Merged configuration

Free space Free space

SPOOL1
used space

Free space
SPOOL2 SPOOL2
used space used space
SPOOL1
used space

SPOOL1 SPOOL2 SPOOL2

50 © 2012 IBM Corporation

JES2 Spool Migration
 General restriction (for move and merge migrations):
–The Source Volume cannot be a Mapped Target
• Cannot merge A to B and then move or merge B to C
o Until A no longer exists
–The Source Volume cannot be actively migrating or extending.
–The track size of the Target Volume cannot be less than the Source
Volume
–The Source Volume cannot be stunted
–Must be at z11 $ACTIVATE mode
• You can NOT go to z2 mode once a migration has been requested
–All members must be at release z/OS JES2 V1.13
 Each SPOOL migration requires a separate XCF group
–Used to manage messages for each unique migration
–JES2 limits migration to 5 concurrent migrations per MAS
–Group name is SYSMGxxx
• xxx is the decimal source SPOOL extent
–Use D XCF,COUPLE to display MAXGROUP formatted in CDS

51 © 2012 IBM Corporation

JES2 Spool Migration
 Move migration moves an INACTIVE volume to a new volume
 Upon successful completion
–The Source Volume no longer exists
–The Target Volume exists and is active
• Could be RESERVED if requested on $M SPOOL command
 Source Volume STATUS= values:
–INACTIVE ->MIGRATING ->does not exist
 Target Volume STATUS= values:
–Does not exist ->ACTIVE
 Additional move migration restrictions :
–The Source Volume must be INACTIVE
–Source Volume cannot be in Absolute format (instead, do a merge).
–The Target Volume will inherit the Source Volume Tracks per Track
Group value.
52 © 2012 IBM Corporation
JES2 Spool Migration

Merge migration moves a Source Volume to an free space

on an active Target Volume
Upon successful completion
–The Source Volume still exists but is STATUS=MAPPED
• Still displays in $DSPOOL and in $DJQ,SPOOL lists
–The Target Volume is a mapped on volume

Source Volume STATUS= values:

–INACTIVE ->MIGRATING ->MAPPED

Additional merge migration restrictions

–The Target Volume must be Active (can be Reserved).
–The Target Volume cannot be stunted.
–The Target Volume must use relative addressing..

53 © 2012 IBM Corporation

 JES3 V1.13 Enhancements
JES3 Dynamic Spool Addition
 Previously, adding a spool extent was disruptive
• Warm start required
• Disrupted all members in the JESplex
 Can now add spool extents with the *F CONFIG command
–Alternatively, add spool extents with a Hotstart with refresh
 Avoids a complex-wide IPL when adding a spool extent
 Installation by setting up a new member with all JSAM definitions
–Starting with DYNALLOC statements
–Ending with ENDJSAM
■ Or set up a new inish deck with an INCLUDE statement pulling in the
JSAM member
■ Or perform a Hot Restart with the new inish deck

54
■ Or issue the *MODIFY CONFIG,ADD=
© 2012 IBM Corporation
with the new JSAM member
JES3 Dynamic Spool Addition
 JES3 Actions
 JES3 will parse the statements and compare them to the current
configuration
 New extents are added
 New partitions are added
 Deletions are rejected
 Other parameters are changed if possible – currently only the ones on
the OPTIONS statement
 Changes are committed if no errors are found
 If *F CONFIG, new spool extents are made usable only after all locals
connect (or are flushed)
 Note: Flush will now happen automatically when XCF detects the
system left the Sysplex
55 © 2012 IBM Corporation
 DFSMS V1.13 Enhancements
Catalog enhancements
–Catalog PARMLIB member (IGGCATxx)
–Catalog Alias update
–IDCAMS LISTCAT LVL CDILVL
IEBCOPY enhancements
PDSE enhancements
–PDSE Validation Utility
–New PDSE Cache Refresh and User Display Commands
Better OPEN/CLOSE/End of Volume Messages
DADSM Pre / Post Allocation – dynamic exits
56 © 2012 IBM Corporation
Catalog PARMLIB Member (IGGCATxx)
Previously, the only way the customers could customize
their Catalog environment is via
SYS1.NUCLEUS(SYSCATxx) and SYS1.PARMLIB(LOADxx)
–Only 1 line (80 characters) is available and it has been long
filled, preventing any new parameters from being added.
–It prevents customers from changing these parameters once
the system has been IPL'ed
In z/OS V1.13 you can now create your own catalog
PARMLIB member(s) to customize the catalog
environment.
–The parameters can be changed by doing an IPL or a simple
restart of the catalog address space (CAS).

57 © 2012 IBM Corporation

Catalog PARMLIB Member (IGGCATxx)
The following parameters are supported in this line item:
–VVDSSPACE(primary,secondary) – Primary and Secondary
space quantities for VVDS implicit defines in tracks. Default is 10 tracks
for both.
–TASKMAX(n) – Catalog service task upper limit. Default is 180.
Minimum is 24 and maximum is 360.
–NOTIFYEXTENT(n) – Percentage threshold to warn when a
catalog is getting full. Default is 80%.

58 © 2012 IBM Corporation

Catalog PARMLIB Member (IGGCATxx)
 The following Enable/Disable parameters supported via the MODIFY
CATALOG command are also supported in this line item
–DELFORCEWNG(YES/NO) - Enables/Disables the ability to issue a
warning message when attempting to use the DELETE VVDS
RECOVERY and DELETE USERCATALOG FORCE commands.
Default is YES.
–DSNCHECK(YES/NO) - Enables/Disables syntax checking on names
being added to a catalog. Default is YES.
–SYMREC(YES/NO) - Enables/Disables the ability to create a SYMREC.
Default is YES.
–UPDTFAIL(YES/NO) – Enables/Disables the message IEC390I from
been issued when a VSAM update request against a catalog
abnormally terminates. Default is YES.
–VVRCHECK(YES/NO) - Enables/Disables enhanced VVR checking on
VVDS I/O. Default is NO.
–DELRECOVWNG(YES/NO) – Enables/Disables the ability to issue a
warning message when the DELETE UCAT RECOVERY command is
issued. Default is NO.
–EXTENDEDALIAS(YES/NO) –Enables/Disables the ability to create
extension records for user-catalog aliases. Default is NO.
59 © 2012 IBM Corporation
Catalog PARMLIB Member (IGGCATxx)
 Comments begin with /* and end with */. Must fit on a single line.
 Multiple declarations of any parameters are allowed. The last valid value will
be used for the parameter. For example, the following are allowed:
VVDSSPACE(10,10)
VVDSSPACE(14,14)
VVDSSPACE(14,14) will be used as the final value for VVDSSPACE in this case
 No blanks will be allowed between digits.
– For example: VVDSSPACE(1 0, 14) is not valid for a VVDSSPACE(10,14)
declaration
 Input ends with the end of file (EOF).
 All parameters should start and finish on the same line.
 The parameters DO NOT have to start in column one. They must fit entirely
within columns 1 and 71. Any text beyond column 71 will be ignored.
 If an invalid parameter is detected on any line, processing for that line stops
at the last valid parameter on that line. Processing continues at the next line.
60 © 2012 IBM Corporation
Catalog PARMLIB Member (IGGCATxx)
 The PARMLIB member(s) must be created in the PARMLIB
concatenation.
 The IGGCATxx parameters are processed both at IPL and when CAS
is restarted
• F CATALOG,RESTART
■ The IGGCATxx member(s) are optional but, if specified, the
parameters specified within take precedence over the parameters
specified in the LOADxx and SYSCATxx members.
■ The suffixes should be specified in the new IEASYSxx parameter,
CATALOG=(list of suffixes separated by commas).
■ When multiple members are specified, the members are processed
in the order specified.
– Examples:
• CATALOG=AA (specifies one member. No parenthesis needed if only one
member)
• CATALOG=(AA,BB,05) (specifies multiple members. Values in
IGGCAT05 will override those in IGGCATBB and IGGCATAA.)
61 © 2012 IBM Corporation
Catalog PARMLIB Member (IGGCATxx)

Requires one or more PARMLIB members (IGGCATxx) and

populate it with the desired settings.
The suffix (xx) is any 2 alphanumeric or national ($,#,@)
characters; the default is “00” (zeros).
Sample IGGCATxx:
VVDSSPACE(40,50)
TASKMAX(75)
--> Blank line allowed
NOTIFYEXTEN(19) --> NOTIFYEXTENT misspelled. Will be
ignored, and an error is issued.
VVRCHECK( YES)

62 © 2012 IBM Corporation

Catalog PARMLIB Member (IGGCATxx)
 If CATALOG= is specified, and a particular IGGCATxx member on it
is not found, it is skipped. If none of the members are found, the
default PARMLIB member (IGGCAT00) is searched.
■ If CATALOG= is not specified, the default member (IGGCAT00) is
searched.
■ If IGGCAT00 does not exist, then default values are used for the
parameters.
 If invalid values are detected in any of the PARMLIB member(s), the
parameter is ignored and a message displaying the invalid parameter
is issued in the SYSLOG and also to the console if it is a CAS restart

63 © 2012 IBM Corporation

Catalog Alias Update
 Most catalog entries are in “user catalogs”, not the master catalog.
■ Number of aliases a user catalog connector can have is currently
limited by the maximum record size for the master catalog.
–Default of the maximum record size: 32768 bytes (32 KB)
–Catalog records are limited to 32768 byte (32 KB) record size.
–User catalog connectors are catalog records.
■ Currently, only approximately 3,500 catalog aliases are allowed per
user catalog.
■ In z/OS V1.13 a new extension record type ‘V’ for user catalog
connectors was introduced.
–The maximum number of user catalog connector extension records is
255.
■ This allows users to define more aliases per user catalog
–Theoretically, limit is over 500,000 aliases per user catalog

64 © 2012 IBM Corporation

Catalog Alias Update

The function by default is disabled

–IBM recommends customers turn on the switch when all the systems in
a sysplex are z/OS V1.13

■ The switch can be turned ON/OFF via catalog Modify

Commands:
–F CATALOG,ENABLE(EXTENDEDALIAS)
–F CATALOG,DISABLE(EXTENDEDALIAS)

■ The switch can also be turned ON/OFF via a catalog

PARMLIB member IGGCATxx in SYS1.PARMLIB by
specifying:
EXTENDEDALIAS(YES/NO)

65 © 2012 IBM Corporation

IDCAMS LISTCAT LVL CTGCDI

LISTCAT LVL() is good for listing the components of a

VSAM cluster or AIX object, but...
–only shows the data and/or index components if they match
the LVL pattern
z/OS V1.13 introduces a new CDILVL parameter - default
is NOCTGLVL
–e.g., LISTC LVL(XYZ.BASE1) ALL CTGLVL
• XYZ.BASE1.CLUSTER
o XYZ.BASE2.DATA  not shown without CTGLVL
o XYZ.BASE3.INDEX  not shown without CTGLVL

66 © 2012 IBM Corporation

IEBCOPY Enhancements
IEBCOPY elapsed time reductions of 19%-70%* when
–Copying one partitioned data set (PDS) to another
–Unloading a PDS to a sequential data set
–Compressing a PDS
IEBCOPY should not require its caller to be APF
authorized
–As delivered, IEBCOPY still has APF authorization but
adapts to non-APF authorized callers
• Old level of IEBCOPY is still callable as IEBCOPYO
• Undocumented alias of IEBDSCPY now points to IEBCOPYO

Most IEBCOPY storage is below the line but it is now

using buffers above the line
–Benefit for marginal virtual storage constraint conditions
*Note: Performance improvements are based on internal IBM laboratory tests. Your results will vary. I/O performance improvements measured for fully shared zFS ranged from very small to 900%, with the majority
of workload conditions tested falling between 50% and 150%. The actual amount of improvement will depend on the environment (monoplex or Parallel Sysplex) and the type of file processing being done. IEBCOPY
improvement will depend on the amount of data being copied, the record format, the record length, and the block size.
67 © 2012 IBM Corporation
 Scalability and Performance …
IEBCOPY Performance*

* IBM Laboratory results; your results may vary. Measured IEBCOPY performance improvements varied with the amount of data being copied,
block
68 size, record format, and record length. © 2012 IBM Corporation
PDSE Validation Utility
PDSE Validation tool designed to verify the structure of
the PDSE directory.
–First phase of the validation tool was integrated into z/OS
1.12 to identify corrupt PDSE’s in LNKLST and at NIP time.
The PDSE validation utility may be invoked using job
control statements, PGM=IEBPDSE. The optional PARM
keyword may be specified.
–PARM=[DUMP|NODUMP]
• If the DUMP option is specified, the PDSE validation utility will issue
an ABEND in the PDSE address space when an error has been
found in the analysis of the PDSE.
–Note: The PDSE validation utility does not validate the
data in the members.
–IEBPDSE does not require APF authorization.
69 © 2012 IBM Corporation
PDSE Validation Utility - Examples
 Example 1: will validate IBMUSER.SIMPLE.V2.PDSE and send the
results to SYSPRINT.
//STEPCHK EXEC PGM=IEBPDSE
//SYSPRINT DD SYSOUT=A
//SYSLIB DD DSN=IBMUSER.SIMPLE.V2.PDSE,DISP=OLD
 Example 2: will validate IBMUSER.SIMPLE.V2.PDSE and
IBMUSER.SIMPLE.V3.PDSE and send the results to the job log.
//STEPCHK2 EXEC PGM=IEBPDSE
//SYSLIB DD DSN=IBMUSER.SIMPLE.V2.PDSE,DISP=OLD
// DD DSN=IBMUSER.SIMPLE.V3.PDSE,DISP=OLD
// DD DSN=SYS1.TCPIP.SEZALOAD,DISP=SHR

70 © 2012 IBM Corporation

PDSE New Commands
When a PDSE error has occurred, the installation needs to
access what is affected by the error and may need to
refresh the in-storage copy of the data set.
In z/OS V1.13, two new commands are provided:
–The CONNECTIONS command is useful in determining
which jobs are affected when an error occurs associated
with a PDSE. The installation can then determine if a reIPL
or restart of the PDSE address space must be done
immediately.
• D SMS,PDSE<1>,CONNECTIONS,DSN(pdsename)<,VOL(volser)>

–The REFRESH command is useful in discarding what may

be bad data for a PDSE after an error.
• V SMS,PDSE<1>,REFRESH,DSN(pdsename)<,VOL(volser)>
71 © 2012 IBM Corporation
Better OPEN/CLOSE/End of Volume Messages
 Open, Close, End of Volume and the OPEN or CLOSE access method
executors detect hundreds of error conditions that result in ABEND
message that contain a numeric ABEND code and return codes with little
English.
 z/OS V1.13 provides an installation option via DEVSUPxx to additionally
include descriptive text appended to the associated ABEND message,
eliminating the need to reference the message manuals to interpret the
ABEND and return codes.
 Originally, the new DEVSUPxx PARMLIB keyword to request that the error
description be appended to the determinant ABEND message:
• OCE_ABEND_DESCRIP={YES | NO}
• The default is NO.
 Example of the output:
– IEC146I 513-08,IFG0196T,CRTAAL1,CRTTSL1,SYSUT2,0920,,DATASET1 036
– ERROR DESCRIPTION:
– A LABEL VIOLATED THE PUBLISHED STANDARD FOR THAT LABEL, AND THE LABEL
– VALIDATION EXIT ISSUED A RETURN CODE REQUESTING OPEN OR EOV TO REJECT
– THE VOLUME.
– END ERROR DESCRIPTION: IEC146I

72 © 2012 IBM Corporation

Better OPEN/CLOSE/End of Volume Messages
APARs OA37957 and OA37505
 New Function to allow verbose message lines contained in a multi-line
message (MLWTO) to be included in the JOBLOG but removed before
they are written to the SYSLOG/OPERLOG, sent to another system, or
queued to a console.
 APAR OA37957 will allow verbose message lines of a multi-line WTO to
be suppressed from SYSLOG/OPERLOG or consoles, leaving them
solely in JOBLOG.
–New .MSGOPTION statement in an active MPFLSTxx PARMLIB member
specifies whether verbose message lines of a multi-line WTO are to be
suppressed.
–MPFLSTxx (message processing facility list) Syntax for controlling the
production of verbose messages
• To control the production of verbose messages, MPFLSTxx recognizes one
statement type .MSGOPTION.
• .MSGOPTION allows you to specify whether verbose messages are to be
produced by the components of your system.
o The syntax of the .MSGOPTION statement is:
» .MSGOPTION VERBOSE (Y)
73
(N) - default
© 2012 IBM Corporation
Better OPEN/CLOSE/End of Volume Messages
APARs OA37957 and OA37505
APAR OA37505 provides DFSMS support for .MSGOPTION
VERBOSE (Y)
With the application of APAR OA37957 and OA37505, the
OCE_ABEND_DESCRIP keyword has no effect.
–If you code any value for this keyword, the system issues message:
• "IEA253I OCE_ABEND_DESCRIP NO LONGER HAS AFFECT. USE
MPFLSTxx MEMBER".

74 © 2012 IBM Corporation

DADSM Pre / Post Allocation – Dynamic Exits
IGGPRE00 and IGGPOST0 are now dynamically
replaceable!
–No need to IPL
–Multiple exits are supported
–Satisfies MR1207046307, MR0328072150, SSMVSS07008, and
partial implementation of MR0220035354
–DADSM takes action according to the highest return code from any of
the exits for IGGPRE00_EXIT:
• 0. Continue
• 4. Reject the request on the current volume but DADSM can try another
volume.
• 8. Reject the request and do not try another volume.

–The IGGPOST0_EXIT exit has no return code.

 Examples
• SETPROG
EXIT,ADD,EXITNAME=IGGPRE00_EXIT,MODNAME=IGGPRE01
• SETPROG
EXIT,ADD,EXITNAME=IGGPOST0_EXIT,MODNAME=IGGPOST5
75 © 2012 IBM Corporation
 BCP (SMF) V1.13 Enhancements
SMF Allow Archive or Delete of an entire SMF
logstream
SMF IFASMFDL stop reading before end of
logstream
SMF Improved Statistics Summary Report

76 © 2012 IBM Corporation

SMF Allow Archive or Delete of an entire SMF logstream
 Previously, it was not possible to archive and delete an entire
logstream
–This limited configuration options for customers when setting up SMF
logstream recording.
 In z/OS V1.13, a method is provided so that the ARCHIVE and DELETE
operations can operate on the entire logstream.
 Being able to ARCHIVE or DELETE the entire logstream provides better
migration options for customers who want to use SMF logstream
recording.
–Without this support if an ARCHIVE or DELETE of an entire logstream is
attempted IFASMFDL will fail and an IFA832I message will be issued
–With SMF data set recording it is very common to see JCL that DUMPs
and CLEARs a data set.
• The same JCL would be reused without requiring changes to the JCL.
–Now with this support a similar concept is available.

77 © 2012 IBM Corporation

SMF Allow Archive or Delete of an entire SMF logstream
 Take the following SYSIN to IFASMFDL as an example:
LSNAME(IFASMF.MULTSYS.STREAM1,OPTIONS(ARCHIVE))
OUTDD(DUMP01,TYPE(0:255))
RELATIVEDATE(BYDAY,0,1)
The RELATIVEDATE parameter here will set the end time of selection to the date
and time that the job was submitted
 In the past this job would be at risk of failing if every thing in the
logstream was selected.
– This would be a race between IFASMFDL and any SMF record writers.
 Now IFASMFDL will write a marker into the logstream to allow for the
deletion of all of the data selected.
– No new parameters or command changes
 If the logstream can not be written to this job will still fail.

78 © 2012 IBM Corporation

SMF IFASMFDL stop reading before end of logstream

Previously, IFASMFDL would always read until the end

of the logstream regardless of the specified end date
and time specified.
–SMF data set recording did not have this issue since
each data set contained only a fixed amount of data.
■ Solution
–Provide a new option to allow IFASMFDL to stop reading
the logstream before the end.
• SMARTENDPOINT and SMARTEPOVER(xxxx).
–The SMARTENDPOINT and SMARTEPOVER options
for IFASMFDL can be used to control how much data is
read from the logstream.
–Depending on the configuration this can greatly reduce
the duration of IFASMFDL jobs.
79 © 2012 IBM Corporation
SMF IFASMFDL stop reading before end of logstream

 This support has two new options for the SYSIN of IFASMFDL
–SMARTENDPOINT and SMARTEPOVER(xxxx).
 In z/OS V1.13 we now support SMARTENDPOINT for ARCHIVE and
DELETE.
 SMARTENDPOINT has been available for the DUMP option in z/OS
V1.12 and below with APAR OA31737 and OA34374
– Note that at z/OS V1.12 and earlier SMARTENDPOINT does not support
ARCHIVE or DELETE processing. If it is used the keyword will be ignored.
 The SMARTEPOVER(xxxx) option specifies a value between 0000
and 0200 (2 hrs) that controls the SMARTENDPOINT processing.
–The default is 0200
 Further guidance available in the MVS System Management
Facilities (SMF) SMARTENDPOINT processing uses the following
rules to find the logical end point in the logstream
80 © 2012 IBM Corporation
SMF IFASMFDL stop reading before end of logstream

SMARTENDPOINT processing uses the following rules

to find the logical end point in the logstream:
–Take the specified end time plus the SMARTEPOVER
value. That is the logical smart end point time.
–For each SID found in a logstream keep a table entry
and mark that SID complete when all SIDs have hit the
smart end point time.
–Once all SIDs are accounted for stop reading.
■ This process occurs on a per logstream basis.

81 © 2012 IBM Corporation

SMF IFASMFDL stop reading before end of logstream

New message IFA844I issue when SMARTENDPOINT

processing is used.
–It lists the SIDs encountered in each logstream that was
processed with SMARTENDPOINT.
– IFA844I THE FOLLOWING SIDS ARE PRESENT IN lsname
sid1 sid2 sid3 sid4 ....

–In the message text:

• lsname – is the name of the logstream.
• sidn – is the SID value for the z/OS image.

82 © 2012 IBM Corporation

SMF Improved Statistics Summary Report
 Currently the Summary Statistics Report written by IFASMFDL
provides the date range of data read in all logstream.
■ There was no way to quickly tell what data was processed (written
and/or deleted) from any given logstream.
■ New message IFA846I will now be displayed for all operations (DUMP,
ARCHIVE, DELETE) and it will detail the range of data processed for
each logstream.
IFA846I PROCESSED DATA RANGES FOR LOGSTREAMS
LSNAME START DATE/TIME END DATE/TIME
IFASMF.MULTSYS.STREAM3 11/05/2010 12:02:00 11/05/2010 12:06:00
IFASMF.MULTSYS.STREAM2 11/05/2010 12:03:00 11/05/2010 12:06:00

83 © 2012 IBM Corporation

SMF Enhancements – available for earlier z/OS releases

 This support was rolled back to z/OS V1.11 and is available

via the following PTFs for APAR OA34589:
–HBB7760 UA58910
–HBB7770 UA58911

84 © 2012 IBM Corporation

 HCD V1.13 Enhancements
HCD Warning if device subchannel set
mismatch
HCD Check for PPRC Secondary Device
HCD Warning when changing local system
name
HCD IODF Consistency check
HCD Partition usage reporting

85 © 2012 IBM Corporation

HCD Warning if device subchannel set mismatch

When defining a device the subchannel set number in the

device-to-processor and the device-to-OS definitions
must match; otherwise the device can not be used.
When you change a device subchannel set ID in the
device-to-processor definition, and this subchannel set
ID is not used in any device-to-OS definition for this
device, HCD now issues the existing information
message CBDG534I earlier in the process, so that you
can adjust the subchannel set ID definition before
building the production IODF.
•CBDG534 'Device xxxx (range nnn) specifies
different subchannel set numbers for its processor
and operating system definitions.'

86 © 2012 IBM Corporation

HCD Check for PPRC Secondary Device
If a PPRC secondary device D/T3390D is contained in the
OS configuration (in an alternate subchannel set), a
corresponding base device D/T3390B must be defined in
subchannel set 0.
When building a production IODF, HCD checks for each
OS configuration of type MVS with a connected 3390D
device, that a 3390B device with the same device number
is also connected to this OS configuration.
If the 3390B device is missing, HCD issues the CBDA398I
warning message.
■ CBDA398I 'PPRC secondary device xxxx in OS
configuration xyz does not have a PPRC
primary device defined in subchannel set 0.'
87 © 2012 IBM Corporation
HCD Warning when changing local system name
 The source and target CHPIDs of a CIB coupling connection are each
given the local system name of the processor to which they will
connect.
 A change of the local system name of a processor that has a CIB
connection to another processor changes also the configuration of
this other processor.
 An activation is required for both processor configurations. In case
of a stand-alone CF processor, a POR would be required.
 Therefore, HCD issues the CBDG400I warning message to make
users aware of the consequences whenever a user changes a
processor's local system name.
CBDG400I 'Change of local system name of processor
proc1 causes a change of the I/O configurations for the
following processor(s): proc2 ...'.
88 © 2012 IBM Corporation
HCD IODF Consistency check

In z/OS V1.7 There was a new profile option,

CHECK_IODF, which you can specify to perform an
automatic check for consistent IODF data when the
currently allocated IODF is switched or the HCD dialog is
terminated.
In z/OS V1.13, HCD now also invokes the IODF checker
whenever a general validation of completeness and
consistency of the IODF is performed, for example, if you
build a production IODF or a validated work IODF.
If a defect is detected in the IODF, the following message
is issued:
CBDA999I 'Defect(s) detected in IODF dsn'
89 © 2012 IBM Corporation
HCD Partition usage reporting
Previously, HCD generated control unit and device
definitions for a CF CHPID only if the target CHPID of the
CF connection connects to a partition with usage type CF
or CF/OS.
However, the HCD CF Channel Path Connectivity
list/report only shows the partition names but not their
usage types
The Channel Path List is enhanced to show the partition
usage type for each partition.
–The usage type is displayed in the partition legend above the partition
matrix, which is visible when scrolling to the right.
–In addition, the PCHID column has been placed next to the CHPID
column.

90 © 2012 IBM Corporation

HCD Partition usage reporting

CF Channel Path Connectivity List:

Column CF indicates whether CHPID is
connected to a partition with usage type
CF or CF/OS.

CF CH ANN EL PAT H C ON NEC TIV ITY RE POR T TIME: 09:07 DATE: 2010 -09 -10 PAGE F- 4
PRO CES SOR ID BR UIC M5 TY PE 209 7 MODEL E64 CONFIGURATION MODE: LPAR
-- --- --- --- --- - S OUR CE --- --- - ------------ --- --- -- DE STI NAT ION -- --- --- --- --- --- --- -- - SOURCE --- - - DESTINATION -
A CCE SS/ CAN D PROCESSOR ACCESS/CAND C NTR L D EVI CE CNT RL DEV ICE CN TL
CH PID TY PE MOD E O L IST ID TYPE-MODEL C HPID TYPE MODE LI ST UNIT NUM,RANGE UNIT NUM,RANGE TY PE
__ ___ ___ ___ ___ ___ __ ___ ___ ___ _ _______________________ _______________ ____________ _ ___ ___ ___ ___ __ ___ ___ ___ ___ ___ __ __
CF Channel Path Connectivity 0. FA IC P SPA N N P LXC SYC 1 BRUICM5 2097-E64 0 .FB ICP SPAN PLXCS YC1 F EC8 F EC0 ,7 FEC 8 FEC 0,7 CF P

Report: 2. FA
P LXC SYC 2
*P LXC CF1 2.FB
PLXCSYC2
*PLXCCF1
F EC8 ,7 FEC 8,7

- --- --- --- --- --- --- --- --- --- --- --- --- --- ----------- --- --- --------------------------------------- --- --- --- --- --- --- --- --- --
Asterisk before partition name 0. FB IC P SPA N N P LXC SYC 1
P LXC SYC 2
BRUICM5 2097-E64 0 .FA ICP SPAN PLXCSYC1
PL XCS YC2
FEC8 FEC0 ,7
F EC8,7
FEC 8 FEC 0,7
FEC8,7
CF P

indicates that the partition 2. FB *P LXC CF1

2. 04 CF P SHR N *P LXC CF1 BRUICM5 2097-E64

2.FA

2 .07 CFP SHR

*PLXCCF1
-- --- --- --- --- --- --- --- --- --- --- -------------------------------------------------- --- --- --- --- --- --- --- --- --- --- --- --- ----
TESTOS FED 8 FED 0,7
usage type is defined as CF or TESTOS
*P LXA CF1 (C )
FED8,7
FFF 9,7

CF/OS. -- --- --- --- --- --- --- --- --- --- --- -------------------------------------------------------- --- --- --- --- --- --- --- --- --- --- --- -

L EGE ND FOR AC CES S/C AND LI ST:

- --- ------------------------
* - P ART ITI ON IS OF USA GE TYPE CF OR C F/O S
( C) - P ART ITI ON IS IN CHP ID' S C AND IDA TE LIS T ONLY

91 © 2012 IBM Corporation

 BCP (IOS) V1.13 Enhancements
IOS Improved Channel Path Recovery
Currently, when various types of path-related errors
occur, IOS removes the path only from the one device
on which the error occurred.
It would be beneficial if z/OS were more pro-active when
these types of path-related errors occur.
–Provide improved system resilience following various types of
hardware failures, including fabric and control unit ports by reducing
the elapse time for z/OS to recover from path-related errors.
–The elapsed time is reduced by having the system threshold path-
related errors that occur and recognizing the scope of devices
affected.
–Recovery is then performed for the entire scope of devices impacted
by the failing resource, all at one time.

92 © 2012 IBM Corporation

Improved Channel Recovery

In z/OS V1.13, IOS will:

–Track path-related errors at the Control Unit level and will,
at a threshold point (# of failures in specific time interval),
respond by removing the failing path from all devices in the
Control Unit.
–Respond to flapping links conditions and dynamic pathing
errors by removing the failing path from all devices in the
Control Unit.

93 © 2012 IBM Corporation

Improved Channel Recovery
I/O Recovery for Failing Path - Before

Device Path Fails

Application I/O Application I/O

I/O 1 I/O n
Volume 1 Volume n

ERP VARY ERP VARY

ERP Retry ERP APR PATH ERP Retry ERP APR PATH

Client Impact

94 © 2012 IBM Corporation

Improved Channel Recovery
I/O Recovery for Failing Path - After

Device Path Fails

Application I/O
Application I/O
I/O 1 I/O n
Volume 1 Volume n

New
Error Events ERP APR Recovery

Client Impact

95 © 2012 IBM Corporation

Improved Channel Recovery
■ IECIOSxx PARMLIB Member
■ Command: SET IOS=xx
■ Statement:
RECOVERY PATH_SCOPE={CU|DEVICE} default: DEVICE
,PATH_INTERVAL=nn default: 10
,PATH_THRESHOLD=nnn default: 10

Note: PATH_INTERVAL and PATH_THRESHOLD can only be

specified with PATH_SCOPE=CU

WARNING: Don't set both the interval and threshold to very low
values (e.g., 1) as this may cause z/OS to remove paths
unnecessarily.

96 © 2012 IBM Corporation

Improved Channel Recovery
PATH_SCOPE={CU|DEVICE}
– Specify CU to enable the path recovery function for an LSS. When a path related
error occurs for a device that results in the path being taken offline, the path will
also be taken offline to all devices in the LSS, unless that would remove the last
path. In addition, IOS will monitor devices for path related errors and take the path
offline when the number of errors exceeds a threshold. Specify DEVICE to disable
the path recovery function for an LSS. This keyword is independent of the
LIMITED_RECTIME and DEV keywords. Changing this value will not affect
actions previously taken.
– Default: DEVICE

PATH_INTERVAL=nn
– Specifies the length of monitoring interval in minutes. Valid values are 1 through
10, where 10 is the default. This keyword can only be used when PATH_SCOPE
has been set to CU. This keyword is independent of the LIMITED_RECTIME and
DEV keywords. Changing this value will not affect actions previously taken.

PATH_THRESHOLD=nnn
– Specifies the number of errors that must be seen for each each minute in the
specified interval before IOS takes action. Valid values are 1 through 100, where
10 is the default. This keyword is independent of the LIMITED_RECTIME and
DEV keywords. Changing this value will not affect actions previously taken.
97 © 2012 IBM Corporation
Improved Channel Recovery
DISPLAY IOS,RECOVERY now displays the following new
information:

IOS103I hh.mm.ss RECOVERY OPTIONS

PATH RECOVERY SCOPE IS BY CU
PATH RECOVERY INTERVAL IS nn MINUTES
PATH RECOVERY THRESHOLD is nnn ERRORS
- or -
PATH RECOVERY SCOPE IS BY DEVICE

98 © 2012 IBM Corporation

Improved Channel Recovery

■ When a path-related error occurs, it can be difficult to

determine where the problem resides. Is it in the switch
card attached to the channel, the link between the
channel and switch or what?
■ In z/OS V1.13, IOS issues a new message with the
IOS050I and IOS051I messages issued for path-related
errors to identify the component that detected the error.
IOS050ICHANNEL
IOS050I CHANNELDETECTED
DETECTEDERROR
ERRORON
ONddddd,yy,op,stat,
ddddd,yy,op,stat,
PCHID=pppp
PCHID=pppp
IOS054Iddddd,pp
IOS054I ddddd,ppERRORS
ERRORSDETECTED
DETECTEDBY
BYcomp,
comp,comp,…
comp,…
Wherecomp
Where compisisone
oneor
ormore
moreofofthe
thefollowing:
following:
CHANNEL,CHAN
CHANNEL, CHANSWITCH
SWITCHPORT,
PORT,CU CUSWITCH
SWITCHPORT,
PORT,CONTROL
CONTROLUNIT
UNIT

99 © 2012 IBM Corporation

Improved Channel Recovery
 This new message is displayed when a path-related error occurs
and the installation has specified PATH_RECOVERY=CU option in
the IECIOSxx member of SYS1.PARMLIB or via the SETIOS
command. The system will attempt to vary the path offline for all
devices in the control unit.
 IOS210I PATH RECOVERY INITIATED FOR PATH pp ON CU
cccc, REASON=rsntxt
–Rsntxt :
• LINK RECOVERY THRESHOLD REACHED
• PATH ERROR THRESHOLD REACHED
• DYNAMIC PATHING ERROR
• REQUESTED BY DEVICE ERP ROUTINE

100 © 2012 IBM Corporation

Improved Channel Recovery
Proactively Removing Paths – Path Error Thresholding:
IOS050ICHANNEL
IOS050I CHANNELDETECTED
DETECTEDERROR
ERRORON
ONdddd,yy,op,stat,
dddd,yy,op,stat,
PCHID=pppp
PCHID=pppp
IOS210IPATH
IOS210I PATHRECOVERY
RECOVERYINITIATED
INITIATEDFOR
FORPATH
PATHpp
ppONONCU
CUcccc,
cccc,
REASON=PATHERROR
REASON=PATH ERRORTHRESHOLD
THRESHOLDREACHED
REACHED

Proactively Removing Paths - Flapping Links:

IOS001Edddd,INOPERATIVE
IOS001E dddd,INOPERATIVEPATHS
PATHSpp pppppppp
pp
IOS2001Idddd,INOPERATIVE
IOS2001I dddd,INOPERATIVEPATHS
PATHS
STATUSFOR
STATUS FORPATH(S)
PATH(S)pp,pp,pp....
pp,pp,pp....
LOGICALPATH
LOGICAL PATHISISREMOVED
REMOVEDOR ORNOTNOTESTABLISHED
ESTABLISHED(A0)
(A0)
LINKRECOVERY
LINK RECOVERYTHRESHOLD
THRESHOLDEXCEEDED
EXCEEDEDFORFORLOGICAL
LOGICALPATH
PATH(06)
(06)
IOS210IPATH
IOS210I PATHRECOVERY
RECOVERYINITIATED
INITIATEDFOR
FORPATH
PATHpp
ppON
ONCU
CUcccc,
cccc,
REASON=LINKTHRESHOLD
REASON=LINK THRESHOLDEXCEEDED
EXCEEDED

101 © 2012 IBM Corporation

Improved Channel Recovery
DISPLAY M=DEV(dddd,(chp)) now displays the reasons why the path is offline.
DISPLAY M=DEV(dddd,(chp))
IEE174I hh.mm.ss DISPLAY M idr
DEVICE nnnn STATUS=status
CHP nn
ENTRY LINK ADDRESS la
DEST LINK ADDRESS la
PATH ONLINE Y|N
CHP PHYSICALLY ONLINE Y|N
PATH OPERATIONAL Y|N
MANAGED Y|N
CU NUMBER CCCC
DESTINATION CU LOGICAL ADDRESS=da
SCP CU ND =tttttt.mmm.nnn.pp.ssssssssssss.uuuu|NOT AVAILABLE
ACTUAL CU ND =tttttt.mmm.nnn.pp.ssssssssssss.uuuu|NOT AVAILABLE
SCP TOKEN NED =tttttt.mmm.nnn.pp.ssssssssssss.uuuu|NOT AVAILABLE
ACTUAL TOKEN NED =tttttt.mmm.nnn.pp.ssssssssssss.uuuu|NOT AVAILABLE
SCP DEVICE NED =tttttt.mmm.nnn.pp.ssssssssssss.uuuu|NOT AVAILABLE
ACTUAL DEVICE NED =tttttt.mmm.nnn.pp.ssssssssssss.uuuu|NOT AVAILABLE
RNID =tttttt.mmm.nnn.pp.ssssssssssss.uuuu|NOT AVAILABLE
NOT OPERATIONAL REASON TEXT
PAV BASE AND ALIASES PP
[PATHS NOT VALIDATED]
[PATH OFFLINE DUE TO THE FOLLOWING REASON(S)]
[PATH RECOVERY ERROR]
[BY OPERATOR]
[CONTROL UNIT INITIATED RECOVERY]
[CONFIGURATION MANAGER]
102 © 2012 IBM Corporation
Improved Channel Recovery

 When the path-related error has been corrected, the path taken
offline to the devices on the control unit can be restored by the
following commands:

– VARY CU
• Recommendation: first issue a VARY DEVICE or VARY PATH for 1
device or path to check whether success is achieved before issuing VARY
CU for all devices or paths

– VARY PATH

– VARY DEVICE

– CONFIG CHP

103 © 2012 IBM Corporation

 z/OSMF V1.13 Enhancements
z/OSMF new management tasks
–Performance: Capacity Provisioning
–Software: Deployment Attend z/OSMF Software
–z/OS Classic Interface: ISPF Deployment – Hands On Lab
Fri – 8AM
z/OSMF new base capabilities Pine (Omni Hotel CNN Center)
–Application Linking
–Authorization update
z/OSMF enhancements
–Existing Management tasks
• Configuration Assistant
• Incident Log
• Workload management
• Resource Monitoring and System Status
–Base enhancements
• Configuration and Setup
104 © 2012 IBM Corporation
Performance: Capacity Provisioning New

New! – view the status of z/OS capacity provisioning domains

 System z On/Off Capacity on Demand
– Ideal if your business has few periodic workload peaks over the year.
– Save on hardware - No need to purchase hardware, ‘you rent it’ for the days you need
it.
– Save on monthly software charges – only pay for software charges for On/Off CoD peak
capacity in the month it is incurred**
– Also ideal if you own extra hardware capacity (banked capacity).
– Save on monthly software charges – budget for peak ‘banked’ capacity and turn off the
resources when not needed to possibly gain software savings.

 z/OS Capacity Provisioning Manager can automate On/Off CoD for z/OS
– Can manage processing capacity more reliably, more easily, and faster.
– What had taken minutes or hours to discover, identify, decide, and resolve, now can be
specified to happen automatically in as little as two minutes.

 New z/OSMF Capacity Provisioning task

– Initial phase simplifies the monitoring of z/OS CP connections, domains,
configurations, and policies
– Separate Windows-based tool required for z/OS CP management functions.
105 © 2012 IBM Corporation
z/OSMF Software Deployment New

New! - simplified deployment of installed software

 New task designed to make deployment of installed software simpler
and safer
– Easy to follow checklist replaces manual and error prone procedures with a user friendly
application
– Incorporates IBM recommended best practices for software deployment.

 Software Deployment can clone software

– Locally, single system or within a sysplex
– Remotely, across a network, and multiple
sysplexes

 Software Deployment can also:

– Identify, modify, delete software instances
– Generate jobs to copy a software instance
– Verify cross-system and cross-product
requisites, verify fixes
– Copy ALL parts of the software (copy the
SMP/E CSI inventory too)

 Clones all SMP/E installed software!

– IBM, ISV, z/OS stack, or individual products
106
– Service upgrades for all of the above© 2012
(viaIBMcomplete
Corporation
replacement)
Classic Interface: ISPF
New

New web-enabled
ISPF interface in
z/OSMF R13

Used by Incident
Log application
Can be linked to
by other z/OSMF
applications
Can be used for
other ISPF
applications
107 © 2012 IBM Corporation
Application Linking New

Example, link Incident Log to SDSF in context

 A more seamless
experience when working
with z/OS
 Make your own linkages
between z/OSMF apps and
even to any web-based apps

 Define an ‘event’ (such as Action from the Incident Log:

Launch to view job status - SDSF
“View Job Status”)

 Then define the ‘event

handler’ action and
parameters (such as ‘go to
ISPF’ with context of the
job)

108 © 2012 IBM Corporation

z/OSMF Administration: SAF-based Authorization
z/OSMF is enhancing its authorization model to
provide tighter integration with Enterprise Security
Management products.
–New resource class pair for z/OSMF
• ZMFAPLA resource class
• GZMFAPLA grouping class
–Use of SAF groups to represent z/OSMF roles
• connection of z/OSMF users to these new Groups
–Resource names associated with all z/OSMF tasks and links.
–Resource class profiles control authorization to z/OSMF
managed resources.
Support for custom roles via creation of additional SAF
groups at system programmer’s discretion. Granularity of
access determined by z/OSMF resource profile
permissions for a given group.
109 © 2012 IBM Corporation
z/OSMF Administration: SAF-based Authorization
Option to stay with repository mode or convert to
SAF mode
–Can switch to SAF mode at a later time
• Configuration support for conversion to SAF mode via scripts.
• Requires activation of ZMFAPLA resource class
o Enable for generic profiles if needed.
–Ability to switch back to repository mode if needed. Not
recommended to switch back and forth repeatedly. SAF
mode is the strategic destination.

Users, Roles (groups) and Task authorization

management
–SAF Mode: via enterprise security management and
customer security change control processes.
–Repository Mode: via z/OSMF Users and Roles tasks
110 © 2012 IBM Corporation
 Config. Assist. for z/OS Communications Server
Updates for z/OSMF R13
 Retrieving TCP/IP profile information from active TCP/IP stacks, enabling it
to import lists of IP addresses that are available for policy configuration.
 Allowing a single instance of the Configuration Assistant to be used to
configure both z/OS V1.12 and z/OS V1.13 Communications Server.
– This is intended to allow you to configure systems in a mixed-release environment from
a single instance of the Configuration Assistant running under z/OSMF.

 Allowing a policy rule to be defined once for multiple stacks, to permit more
efficient policy configuration for multiple systems without having to
individually define every policy rule for every stack.
 z/OS Communications Server intrusion detection services (IDS) technology
is enhanced to add support for IPv6 traffic and also additional attack types,
including Enterprise Extender, data hiding, and out of sequence packet
denial of service attacks.

111 © 2012 IBM Corporation

Incident Log
Updates for z/OSMF 1.13
FTP destination and Firewall Proxy settings shared with
Software Deployment
– Can be updated during the wizard
– Can be locked for update

The name of file being transmitted is also included in the

message
Support the Problem Documentation Upload Utility included
with z/OS as of R13
Use of system temporary dataset for working with Unix files
also – compressing before sending
APAR search string added in the View Diagnostic Details
panel
Application linking to ISPF to browse log snapshots
112 © 2012 IBM Corporation
z/OSMF Workload Management
Updates for z/OSMF R13

Separate authorization
levels for
– Viewing of service definitions,
– service policies, and WLM status
– Installation and activation of service
policies
– Modification of service definitions

Settings of a user are

persisted between
sessions
– Sorting/filtering/configuration of
(tree)-table columns
– Recently used data set names
during import/export of service
definitions
– Selections in Print Preview Filter
dialog
– Selections in Export to Local
Workstation dialog
113 © 2012 IBM Corporation
Resource Monitoring
Updates for z/OSMF V1R13

The following tasks have been renamed

–Sysplex Status has been renamed to System Status
–Monitoring Desktops has been renamed to Resource Monitoring
• The Desktops have been renamed to Dashboard

With z/OSMF V1.13, RMF provides new CIM-based

performance data gatherers for:
–Linux on System z,
–Linux on System x, and
–AIX systems
providing a consistent monitoring solution for
zEnterprise ensembles.
• This is intended to display performance metrics from those platforms and
combine them with z/OS metrics in common graphic views

114 © 2012 IBM Corporation

Integrated z/OS and Linux resource monitoring
A monitoring solution for multi-tier workloads

 Monitor the resources for z/OS

and Linux workloads

 Ideal for use with System z

Processor Utilization
Enterprise System of Linux Processes

 For z/OSMF R12

– Use separate as-is, no-charge
web-download tool to gather
resource information for Linux for
System z and Linux for x86
systems.

 For z/OSMF R13

– New performance data gatherers
for Linux on System z, Linux on
IBM System x®, and AIX® systems
integrated in z/OSMF
– Consistent monitoring solution for
these systems in zEnterprise Processor Utilization
ensembles. of z/OS Jobs
Note, screen capture from z/OSMF R12

115 © 2012 IBM Corporation

z/OSMF V1.13 Configuration Enhancements (1 of 2)
 Command simplification
– Can provide a single file to define global settings or environment
variables and export the location of the file to your shell session.
– -file and -override file parameters will pre-pend IZU_CONFIG_DIR if
no path is specified.
– Configuration and override files are kept in the configuration directory
and managed by the scripts
– Script log files and report files are written to the z/OSMF log file
directory, which is identified by the IZU_LOGFILE_DIR environment
setting for the UNIX shell.
• By default, this directory is /var/zosmf/configuration/logs/.
– Flexibility is enhanced through the addition of overrides which allow
you set options globally for any UID or GID values that you choose
not to specify individually.
– z/OS configuration tasks moved to -prime step
• Previously were in -config, -prime and –finish
• -config is now just accumulation of configuration data

116 © 2012 IBM Corporation

z/OSMF V1.13 Configuration Enhancements (2 of 2)
Migration Improvements
–Now supports both override and configuration files
• From any prior supported release
• Can do either, or both at the same time
–Report file is generated

Security Simplification
–Group Management
• Scripts only create groups owned by z/OSMF (Administrator, User,
Storage Administrator).
• Will prompt for and use other groups if known
–Authorization Mode switch
• Can specify either SAF or Repository and then switch later.
• Will generate all necessary commands for this switch
• Authorization of additional users is based on Mode

RAS Items
–Additional messages for better log file documentation and diagnosis
–Temporary file handling is improved
117
–Input validation improved © 2012 IBM Corporation
 z/OS V1.13 Summary
ISPF
–Miscellaneous enhancements
JES2
–“Batch Modernization” enhancements
–Spool dataset enhancements
JES3
–JES3 Dynamic Spool Addition
DFSMS
–Catalog enhancements
–PDSE enhancements
–Miscellaneous enhancements
SMF
–SMF logstream enhancements
HCD
–New warning messages
IOS
–Improved Channel Recovery
z/OSMF
118 © 2012 IBM Corporation
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both.

Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not
actively marketed or is not significant within its relevant market.
Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States.

For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml:

*, AS/400®, e business(logo)®, DBE, ESCO, eServer, FICON, IBM®, IBM (logo)®, iSeries®, MVS, OS/390®, pSeries®, RS/6000®, S/30, VM/ESA®, VSE/ESA,
WebSphere®, xSeries®, z/OS®, zSeries®, z/VM®, System i, System i5, System p, System p5, System x, System z, System z9®, BladeCenter®

The following are trademarks or registered trademarks of other companies.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce.
* All other products may be trademarks or registered trademarks of their respective companies.

Notes:
Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will
experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed.
Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here.
IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual
environmental costs and performance characteristics will vary depending on individual customer configurations and conditions.
This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without
notice. Consult your local IBM business contact for information on the product or services available in your area.
All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance,
compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.

119
119 © 2012 IBM Corporation