z/os small enhancements - episode 2016a

© Copyright IBM Corporation 2016. Technical University/Symposia materials may not be reproduced in whole or in part without the prior written permission of IBM.

Small z/OS enhancements over the past several releases

Marna WALLE, [email protected]

Member of the IBM Academy of Technology

z/OS System Installation

IBM z Systems, Poughkeepsie NY USA

mailto:[email protected]

© 2016 IBM Corporation2

TrademarksThe following are trademarks of the International Business Machines Corporation in the United States, other countries, or both.

The following are trademarks or registered trademarks of other companies.

* 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.

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.

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®

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.

Notice Regarding Specialty Engines (e.g., zIIPs, zAAPs and IFLs):

Any information contained in this document regarding Specialty Engines ("SEs") and SE eligible workloads provides only general descriptions of the

types and portions of workloads that are eligible for execution on Specialty Engines (e.g., zIIPs, zAAPs, and IFLs). IBM authorizes customers to use

IBM SE only to execute the processing of Eligible Workloads of specific Programs expressly authorized by IBM as specified in the “Authorized Use

Table for IBM Machines” provided at www.ibm.com/systems/support/machine_warranties/machine_code/aut.html (“AUT”).

No other workload processing is authorized for execution on an SE.

IBM offers SEs at a lower price than General Processors/Central Processors because customers are authorized to use SEs only to process certain

types and/or amounts of workloads as specified by IBM in the AUT.

http://www.ibm.com/systems/support/machine_warranties/machine_code/aut.html


• z/OS V2.2:

•ISPF: z/OS UNIX Mounted File Systems

• z/OS V2.1:

SDSF: New system information panels

BCP: SETSMF without PROMPT at IPL

BCP: Logon allocation message

• z/OS V1.13:

DFSMS: PDSE handy commands

BCP and DFSMS: Verbose message control

z/OS V1.12:

•DFSMS: IDCAMS VERIFY with RECOVER

• Older than the hills:

•BCP: Tape Library Load Balancing

•Communications Server: REXX ftp client API

•RACF: Logon statistics suppression

z/OS Little Enhancements - Edition 2016A


= Sysprog

= Sysprog & Users© 2007 IBM Corporation

z/OS V2R2

Little Enhancements

ISPF: z/OS UNIX Mounted File Systems


What: The ISHELL Mount Table is very difficult to work with, especially for a lot of

mounted file systems.

– Can’t find values easily, can’t see consolidated the file system name and

mountpoint, multiple deep steps to get handy information…

z/OS V2.2 ISPF allows easy viewing/changing of the mount table!

– “Twisties” help consolidate similarly named file systems and mount points.

– Think: SMP/E FIXCAT Explorer.

– A helpful find command!

– File systems and mount points are shown together!

How to use:

1. ISPF 3.17, File System -> Mount Table by File System or Mount Table by Mount

Point.

2. Expand, collapse, find, modify at will.

Considerations:

– No PF11 (right) and PF10 (left) support .

– Just try it out, and you’ll never go back to the ISHELL Mount Table.

z/OS V2R2 Enhancements





Existing ISHELL: No find command, but there is an unhelpful locate command.


Three levels deep (when I finally find the file system I want)

to see mount point, file system type, …

Existing ISHELL:




New ISPF 3.17…two excellent “views”:




New ISPF 3.17 “Mount Table by File System”:






New ISPF 3.17 “Mount Table by File System”: xa for “expand (and collapse) all

Can xa on the command

line for all file system

names too.




New ISPF 3.17 “Mount Table by File System”: easily understood hierarchy.

Notice file system and mount point are clearly identified together!




New ISPF 3.17 “Mount Table by File System”: easy find!


New ISPF 3.17 “Mount Table by Mount Point”: … the reverse view






(Options -> Mount Table Column Arrangement)

Mount Table Mount Point customization:

Mount Table File System customization:


© 2007 IBM Corporation

z/OS V2R1

Little Enhancements

= Sysprog

= Sysprog & Users





What: An SPE on z/OS V2.1 and V2.2 SDSF (PI43902, and a BCP PPT

update in OA48578), you can easily see system information:

– SYS - System information

– LNK – Link list data sets

– LPA – Link pack data sets

– APF – APF data sets

– PAG – Page data sets

– PARM – Parmlib data sets

– …and SRCH within the returned data sets for members!

How to use:

1. Set up SDSFAUX address space

2. Start enjoying the new panels.

z/OS V2R1 SPE Enhancements



Set up SDSFAUX address space

– SDSF server address space continues to be optional (and recommended!) The server must

be started to use this new function.

– When SDSF server is started, the new SDSFAUX address space is automatically started.

– SDSFAUX will automatically stop when SDSF server is stopped.

– Only one SDSFAUX per system, and can be used by multiple SDSF servers.

– Can start manually with S SDSFAUX (and stop with P SDSFAUX)

Considerations:

– Recent APARs PI54862 and PI56151 may help.

– APAR= PI54862: ISF452E SDSFAUX COMMUNICATIONS FAILED, RETURN CODE

0X00000008, RC= 0X00360806" RECEIVED WHEN USING NEW SDSF COMMANDS

– APAR= PI56151: MESSAGE HSF0067E CSVDYLPA ADD FOR MODULE HSFSRVRM

FAILED RC=4 RSN=00000401 DIAG=20004001.AT SDSFAUX STARTUP

– Doc for the new function is in SDSF Operation and Customization:

– V2.2: SA23-2274-03

– V2.1: SA23-2274-01




How to set up SDSFAUX:

1. Copy the sample SDSFAUX (which is an alias of HSFSRJCL) from SISFJCL to your

proclib concat, and call it SDSFAUX.

– You can call it something else, but you’d need to update ISFPRMxx to give the name

if you didn’t use SDSFAUX.

– Check the proc, but you shouldn't need to make any updates.

2. SDSFAUX address space requires that SISFLOAD be in either the system linklist (or

be in the STEPLIB or JOBLIB).

3. Set up security for SDSFAUX address space.

– SAF SDSF class must be RACLISTed.

– Define userid associated with SDSFAUX address space (same as SDSF server is

fine).

– Add a profile in the STARTED class for SDSFAUX.* (or you can use your existing

SDSF*.* which is also fine).

4. Set up security for new panels for users. Plenty o’ profiles to control commands on

new panels.





SDSF: New system information panels - SYS



SDSF: New system information panels – SYS, DAL



SDSF: New system information panels – LNK



SDSF: New system information panels – LNK, SRCH



SDSF: New system information panels – LNK, SB



SDSF: New system information panels – PAG


= D ASM,LOCAL


SDSF: New system information panels – PAG, DL


What: To use the SETSMF command (prior to V2.1) you had to have specified PROMPT(..)

in SMFPRMxx at IPL. However, folks didn’t want to specify PROMPT(..) at IPL.

– The SETSMF command is less disruptive than a SET SMF=xx command (which resets the

entire parmlib member).

New statement in SMFPRMxx AUTHSETSMF|NOAUTHSETSMF can control whether you want

(or don’t want) to be able to use SETSMF after IPL.

– By allowing SETSMF when NOPROMPT is specified allows the majority of installations to

avoid delays at IPL.

How to use:

Specify AUTHSETSMF in SMFPRMxx at IPL. Keep NOPROMPT if you like.

– You cannot SETSMF to change AUTHSETSMF!

Considerations:

– When AUTHSETSMF is specified, the SETSMF command is authorized, regardless of the

specification of PROMPT or NOPROMPT.

– When NOAUTHSETSMF is specified, the SETSMF command is not authorized, regardless

of the specification of PROMPT or NOPROMPT




z/OS R13: D SMF,O then trying to do a SETSMS command with SMFPRMxx NOPROMPT

IEE970I explanation: The operator entered a SETSMF command. The SMFPRMxx parmlib

member in effect includes the NOPROMPT option, which makes SETSMF an incorrect

operator command.


z/OS V2.1: Added AUTHSETSMF (keeping NOPROMPT) to SMFPRMxx


z/OS V2.1: D SMF,O then doing a SETSMS command with SMFPRMxxAUTHSETSMF and NOPROMPT … SUCCESS!


What: It’s particularly annoying if you are trying out a new logon proc,

have an allocation failure for a referenced data set. This isn’t helpful:

MWALLE LOGON IN PROGRESS AT 18:25:28 ON JUNE 29, 2015

LOGON FAILED ALLOCATION UNSUCCESSFUL

MWALLE LOGGED OFF TSO AT 18:25:28 ON JUNE 29, 2015

IKJ56400A ENTER LOGON OR LOGOFF-

– Now, allocation will issue messages to the terminal to tell you exactly

where the problem is!

How to use:

1. Read new message IEFA107I during logon.

2. Fix the problem you were told about.

Considerations:

– Only indicates the first allocation error. You will have to read and fix

each problem iteratively.






IEFA107I

output



z/OS R13

Little Enhancements

DFSMSdfp: Some PDSE handy commands

BCP and DFSMSdfp: Verbose message control

= Sysprog

= Sysprog & Users


z/OS R13 Enhancements


Background: Two kinds of PDSE corruption: 1) in memory, and 2) on DASD.

SMSPDSE is non-restartable and is used for linklist PDSEs. SMSPDSE1 is restartable, for non-linklist PDSEs.

What: For problem determination, to find where a PDSE is currently being

used.– D SMS,{PDSE|PDSE1},CONNECTIONS,DSN(dsname)[,VOL(volser)]

To help with PDSE corruption in memory, to discard the buffered directory pages for a specific PDSE. (The next access will come from the data set on DASD).– VARY SMS,{PDSE|PDSE1},REFRESH,DSN(dsname)[,VOL(volser)]

To help with PDSE corruption on DASD detection (not correction), use IEBPDSE utility.

– Suggestion: put IEBPDSE as the first step of batch jobs using critical PDSEs.




How to use. A sample non-serialization scenario:

1. You receive message ADR795E or ADR796E

– (ttt)-mmmmm(yy), AN UNEXPECTED RETURN CODE (return_code) AND REASON CODE (reason_code) HAS BEEN RECEIVED FROM THE IGWNOTIF MACRO WHILE PROCESSING VOLUME volume_serial_number (((or DATA SET dsname )))

2. Find out who is using the PDSE:

– D SMS,PDSE1,CONNECTIONS,DSN(MWALLE.UTIL.JOBS)

IGW051I PDSE CONNECTIONS Start of Report(SMSPDSE1)

---------data set name---------------------- -----vsgt-------

MWALLE.UTIL.JOBS 01-ZOS002-000204

--asid-- --name-- --tcb--- -open-

0095 MWALLE 009FF158 Input

PDSE CONNECTIONS End of Report(SMSPDSE1)

3. Try to access the PDSE from another system. If you can access from another system, then the corruption is likely in-storage. (Since buffers are system-specific.)

– Refresh the in-storage buffers for the PDSE:– VARY SMS,PDSE1,REFRESH,DSN(MWALLE.UTIL.JOBS)

IGW052I The cached directory blocks for PDSE MWALLE.UTIL.JOBS have been discarded

4. If you cannot access from both systems, likely the PDSE is corrupted on DASD:

– //STEPCHK EXEC PGM=IEBPDSE,PARM='DUMP'

//SYSPRINT DD SYSOUT=*

//SYSLIB DD DSN=MWALLE.UTIL.JOBS,DISP=SHR


z/OS R13 Enhancements (with OA37957 and OA37505)


What: There are many messages (specifically DFSMS O/C/EOV abend IEC*

messages) which could be more helpful in providing information to the end user.

– You can spend a lot of time looking up a message, just to then have to look the specific return code from a very long list.

– Wouldn’t it be nice if the message just told you in “English” what had happened?

How to use: .MSGOPTION VERBOSE(Y) in MPFLSTxx controls if verbose

messages will be produced.

– VERBOSE(Y) Verbose messages will be produced in the joblog, and extra

lines will not be produced in the syslog or operlog or queued to console.

– VERBOSE(N) Verbose messages will not be produced. Same behavior as it’s

been all along.

Considerations:

Right now, verbose messages are exploited only by these IEC* messages.

Additional verbose message lines are visible in MPF exits and on the Subsystem

Interface (SSI).




Example of not using verbose message control:

D MPF

IEE677I 15.48.20 MPF DISPLAY 941

…

SUBSYSTEMS RECEIVING FOREIGN MESSAGES AND DOMS:

*ALL

MSG OPTIONS: NONE

FIELD -MPF COLOR HLIGHT INTEN FIELD -MPF COLOR …

1.

2.IEF403I BADOPEN - STARTED - TIME=16.03.50

IEC142I 113-2C,IFG0194D,BADOPEN,FIX1,SYSUT1,0981,PAGE08, 016

SYS1.COMMON.DATA

IEA995I SYMPTOM DUMP OUTPUT 017

SYSTEM COMPLETION CODE=113 REASON CODE=0000002C

TIME=16.03.50 SEQ=00010 CPU=0000 ASID=0027

PSW AT TIME OF ERROR 075C1000 80D12336 ILC 2 INTC 0D

NO ACTIVE MODULE FOUND

… Syslog and joblog information




Example of using verbose message control:

3.

SET MPF=MW

IEE252I MEMBER MPFLSTMW FOUND IN SYS1.PARMLIB.POK

IEE712I SET MPF PROCESSING COMPLETE

4.

D MPF

IEE677I 16.04.28 MPF DISPLAY 029

…

SUBSYSTEMS RECEIVING FOREIGN MESSAGES AND DOMS:

*ALL

MSG OPTIONS: VERBOSE

FIELD -MPF COLOR HLIGHT INTEN FIELD -MPF COLOR …

5.




Example using verbose message control: IEF403I BADOPEN - STARTED - TIME=16.04.52


SYS1.COMMON.DATA



TIME=16.04.52 SEQ=00011 CPU=0000 ASID=0027



6.

Syslog informationIEF403I BADOPEN - STARTED - TIME=16.04.52


SYS1.COMMON.DATA

ERROR DESCRIPTION: IEC142I

An OPEN was issued for a VSAM data set with a DCB, but the caller

was not APF authorized or not in supervisor state.

END ERROR DESCRIPTION: IEC142I



TIME=16.04.52 SEQ=00011 CPU=0000 ASID=0027



7.

Joblog information !

(same as in book)

Syslog information



z/OS R12

Little Enhancements

DFSMS: IDCAMS VERIFY with RECOVER

= Sysprog

= Sysprog & Users


What: Using the EXAMINE command for a VSAM data set that was closed

improperly, can result in a cc 8 because of an interrupted VSAM

process.

As of R12, you can complete or back out the interrupted VSAM process by adding the RECOVER parameter to the VERIFY

command.– VERIFY without RECOVER will only update the end of data (EOD) and end of key range (EOKR) catalog

information so that it is accurate when the data set is next opened.

Then, check for any remaining errors using the EXAMINE command

for the data set again.

Consideration: The data set cannot already be opened on any system, or VERIFY RECOVER will fail with an OPEN error.

IBM recommends that you specify the RECOVER parameter after an

improper close of a key-sequenced data set.






Example:

EXAMINE NAME(MWALLE.TESTCSI.CSI) INDEXTEST DATATEST

IDC3300I ERROR OPENING MWALLE.TESTCSI.CSI

IDC3351I ** VSAM OPEN RETURN CODE IS 116

IDC31704I DATA SET IS ALREADY OPEN FOR OUTPUT OR WAS NOT

CLOSED CORRECTLY

IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12

IDC0002I IDCAMS PROCESSING COMPLETE. MAXIMUM CONDITION CODE

WAS 12

1.

2. VERIFY DATASET(MWALLE.TESTCSI.CSI) RECOVER

IDC3300I ERROR OPENING MWALLE.TESTCSI.CSI

IDC3351I ** VSAM OPEN RETURN CODE IS 118

IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0


WAS 0

Attention message: The data set was

not properly closed but OPEN's implicit

verify was successfully processed.




Example:

EXAMINE NAME(MWALLE.TESTCSI.CSI) INDEXTEST DATATEST

IDC01700I INDEXTEST BEGINS

IDC11773I 1 KEYS PROCESSED ON INDEX LEVEL 1, AVERAGE KEY..

IDC11774I CURRENT INDEX CISIZE IS 4096, RECOMMENDED MINIMUM

INDEX CISIZE IS 15

IDC01724I INDEXTEST COMPLETE - NO ERRORS DETECTED

IDC01701I DATATEST BEGINS

IDC01709I DATATEST COMPLETE - NO ERRORS DETECTED

IDC01708I 1 CONTROL INTERVALS ENCOUNTERED

IDC01710I DATA COMPONENT CONTAINS 1 RECORDS

IDC01711I DATA COMPONENT CONTAINS 0 DELETED CONTROL INTERVALS

IDC01712I MAXIMUM LENGTH DATA RECORD CONTAINS 80 BYTES

IDC01722I 99 PERCENT FREE SPACE

IDC0001I FUNCTION COMPLETED, HIGHEST CONDITION CODE WAS 0


WAS 0

3.



Older than the hills

Little Enhancements

BCP: Tape Library Load Balancing

Communications Server: REXX interface for

ftp client

RACF: Logon statistics suppression

= Sysprog

= Sysprog & Users


Older than the hills (z/OS R11, back to R9):


What: A new optional algorithm for all non-specific tape requests (i.e.scratch) to be balanced

across tape libraries based on the number of devices in the library, all other things being equal.

Otherwise (default) the tape requests are equally random across libraries, and may be

“unfair”.

How to use: As expected, use SETALLOC and ALLOCxx:

1. SETALLOC SYSTEM,TAPELIB_PREF=BYDEVICES

– To revert back: SETALLOC SYSTEM,TAPELIB_PREF=EQUAL

2. To make permenant in ALLOCxx: SYSTEM TAPELIB_PREF(EQUAL|BYDEVICES)

3. D ALLOC,OPTIONS To query current options

Considerations:

No prerequisities. All done in Allocation.

If you have only one tape library, or tape libraries with the same number of devices, this new

algorithm will have no effect.

This function is particularly attractive if you are adding new tape libraries (with lots of devices),

and want to reduce a chance of overload onto the older tape libraries (with fewer devices).

Remember to make a dynamic change permanent, to avoid regression.




Example Without Tape Library Load Balancing:

TAPELIB_PREF(EQUAL)

…

1024 tape devices

8 tape devices

Scratch tape request

½ = 50%½ = 50%Equally likely




Example With Tape Library Load Balancing:

TAPELIB_PREF(BYDEVICES)

…

1024 tape devices

8 tape devices

Scratch tape request

1024 / (1024+8) = 99.2%

128 times more likely8 / (1024 + 8) = 0.7%


What: REXX interface means you can easily write programs to use ftp!

– In addition to Java, C, COBOL, PL/I, and assembler.

How to use:

– Handy sample is found in TCPIP.SEZAINST(EZAFTPIR)

– Understand the FCAI stem variables, which represents an instance of use.

– result = ftpapi(stem, request_type, parm1, parm2, ...)

1. ftpapi('fcai.', 'create', mytraceid) create the fcai

2. ftpapi('fcai.', 'init', myserver, myvar1, myvar2) open a connection

3. ftpapi('fcai.', 'scmd', my_subcommand, 'W') do an ftp subcommand

4. ftpapi('fcai.', 'term') terminate the connection, but

you should subcommand quit first to get the trace information.

Considerations: Connecting to an ftp server that can accept an anonymous

userid is ideal. I had to provide my password “in the REXX”, if not.

Doc: z/OS Communications Server: IP Programmer's Guide and Reference

Older than the hills (z/OS R8):

Communications Server: REXX ftp client API




My REXX EXEC, based on EZAFTPIR:




My REXX EXEC SAYs:




My REXX EXEC, FTP connection messages:


What: Allows you to specify which applications should only record the first system access of a

day. This could result in reduced I/O and lowered serialization impacts on the RACF data set.

Affects applications that specify the APPL operand on RACROUTE REQUEST=VERIFY

How to use: APPL profiles are used to specify which applications take advantage of this function.

1. Determine which applications you want to have only the first access of the day recorded.

2. Create or Modify the profile in the APPL class for the application to only record the first

time that day’s access in APPLDATA:

– New: RDEFINE APPL applname UACC(NONE) APPLDATA('RACF-

INITSTATS(DAILY)')

– Then: PERMIT applname CLASS(APPL) ID(userid-or-group)

ACCESS(READ)

– Existing: RALTER APPL applname APPLDATA(‘existing data RACF-

INITSTATS(DAILY)')

3. Activate the APPL class, if necessary: SETROPTS CLASSACT(APPL) RACLIST(APPL)

– If already active and RACLISTed, then refresh: SETROPTS RACLIST(APPL) REFRESH

Considerations: LJDATE, LJTIME, USBD_LASTJOB_DATE, and USBD_LASTJOB_TIME fields

will have the last recorded date and time for that day, not the last actually used for that day.





Summary of What We Might Want to Share:

• System Programmer & User Items:

ISPF (V2.2): z/OS UNIX Mounted File Systems

SDSF (V2.1): New system information panels

BCP (V2.1): Logon allocation message

BCP and DFSMS (R13): Verbose message control

DFSMS (R12): IDCAMS VERIFY with RECOVER

Communications Server (old): REXX ftp client API

• System Programmers’ Items:

BCP (V2.1): SETSMF without PROMPT at IPL

DFSMSdfp (R13): PDSE handy commands

BCP (old): Tape Library load balancing

RACF (old): Logon statistics suppression



z/OS Little Enhancements – Edition 2016A: Summary

• z/OS V2.2:

•ISPF: z/OS UNIX Mounted File Systems Excellent helpful views!

• z/OS V2.1:

SDSF: New system information panels Offers handy in-context

information.

BCP: SETSMF without PROMPT at IPL Better availability and flexibility.

BCP: Logon allocation message A real time saver.

z/OS V1.13:

DFSMS: PDSE handy commands Could save an IPL.

BCP and DFSMS: Verbose message control No more lookup.

z/OS V1.12:

•DFSMS: IDCAMS VERIFY with RECOVER Fix it for availability.

• Older than the hills:

•BCP: Tape library load balancing Treats your tape requests fairly.

•Communications Server: REXX ftp client API Very easy to use.

•RACF: Logon statistics suppression To reduce I/O and contention.