DFSMSdfp
This chapter describes the changes that were made to DFSMSdfp that was introduced with z/OS V2R2.
This chapter includes the following topics:
1.1 DFSMSdfp overview
The DFSMSdfp is a Data Facility Storage Management Subsystem (DFSMS) element that provides the following storage, data, program, and device management:
•Interactive Storage management
DFSMSdfp includes Interactive Storage Management Facility (ISMF), with which you define and maintain policies to manage your storage resources.
•Tape mount management
Tape mount management is a methodology for improving tape usage and reducing tape costs.
•Data management
DFSMSdfp helps store and catalog information on direct access storage devices (DASD) and optical and tape devices so that it can be quickly identified and retrieved from the system.
•Device management
DFSMSdfp can be used when you define your input and output (I/O) devices to the system and in controlling those devices in the z/OS environment.
•Distributed data access
Distributed data access allows all authorized systems and users in a network to use system-managed storage or automated storage management.
•Advanced copy services
Advanced Copy Services includes remote and point-in-time copy functions that provide backup and recovery of data.
•Object access method
Object Access Method (OAM) provides storage, retrieval, and storage hierarchy management for objects.
1.2 DFSMSdfp enhancements
The following DFSMSdfp enhancements are available in z/OS V2R2:
•SMS space constraint relief
•New user-defined Automatic Class Selection (ACS) read-only variable in SMS PARMLIB
•SMS RAS:
– New information console message
– Enhance SELECT/DESELECT command
– Include data set name and storage name in ACS messages
– Display storage groups in IGD17800I
– Externalize IGD17364I to hardcopy log
•Storage group space alert messages
•SMF Volume Table of Content (VTOC) audit log
•DFSMSdfp open/close/end volume
– Tape performance and recovery
– Conversion of tape installation exits
– DEVSUPxx
– SMF 14/15
– Include above the line CSECTs
– Eliminate abend A13-18
These enhancements are described in this chapter.
1.3 SMS space constraint relief enhancements
The space constraint relief enhancements that are described in this section improve data set allocation.
1.3.1 Space constraint relief for guaranteed space allocations
During allocation, there might be insufficient space on a volume to meet the requested space. SMS volume selection might solve the problem for non-guaranteed space allocations by trying all candidate volumes before failing the allocation. Another option is to use the Space Constraint Relief and Reduce Space Up To (%) attributes to request that an allocation be retried if it fails because of space constraints.
In z/OS V2R2, this functionality was extended to guaranteed space allocations to help reduce these types of failures. The SCR space reduction function was enhanced to allocate the largest possible space that satisfies the value (percentage) for guaranteed space and non-guaranteed space requests.
The new subparameter, Guaranteed Space Reduction (Y | N), is added to the Data Class Panel to specify whether space reduction on guaranteed space allocation is permitted. The new subparameter is shown in Example 1-1.
Example 1-1 New subparameter in Data Class Panel
DATA CLASS DISPLAY Page 2 of 5
Command ===>
CDS Name . . . . . : SYS1.STPPLEX.SCDS
Data Class Name . . : EXTADD
Data Set Name Type . . . . . : EXTENDED
If Extended . . . . . . . . : REQUIRED
Extended Addressability . . : YES
Record Access Bias . . . . : USER
RMODE31 . . . . . . . . . . :
Space Constraint Relief . . . : NO
Reduce Space Up To (%) . . :
Guaranteed Space Reduction : NO
Dynamic Volume Count . . . :
Compaction . . . . . . . . . :
Spanned / Nonspanned . . . . :
|
Note: Guaranteed space reduction affects VSAM and non-VSAM data sets and remains unsupported for striping allocation.
|
1.3.2 Space constraint relief for secondary allocation
Before z/OS V2R2, the space constraint relief (SCR) applies only in the Primary Space allocation; that is, SCR was not used if the data set was extended by using the Secondary Space amount of allocation.
A situation can occur in which large amounts of free space that is less than what the user specified for secondary allocation amount is left unused on the current volume, or the allocation can fail when there are no more volumes to be used.
With z/OS V2R2, SCR also applies to secondary allocation.
Another improvement in SCR is to use the largest available extent on volume. Consider a scenario that includes the following parameters:
•Secondary Space allocation of 2000 cylinders
•Reduce Space Up To(%) in Data Class of 90%
•Largest extent available on volume is 1000 cylinders
In this case, when the data set needs another extent, the allocated amount is 1000 cylinders, which represents a 50% of reduction.
To enable space reduction, the Data Class must include the following settings:
•Space Constraint Relief = Y
•Reduce Space Up To (%) > 0
The following new SMF fields were added to track the use of this function:
•SMF64SSR: Indicates whether secondary space reduction was used
•SMF64NTA: Indicates the size of extent that is returned in tracks
This enhancement supports VSAM/VSAM RLS/PDSE/BAM/SAM; however, some VSAM KSDS allocations result in minimum space that is allowed because CATALOG and DADSM cannot find space to allocate INDEX after the largest extent available was used for DATA. To avoid the failure in this case, CATALOG and DADSM return to their previous behavior, which allocates the minimum space allowed that is derived from Reduce Space Up To (%).
|
Note: VSAM and non-VSAM multi-striped data sets do not support SCR. For more information, see DFSMS Using Data Sets.
|
1.3.3 New IGD17296I message
Another enhancement is the new message, IGD17296I. This message is issued to the hardcopy and job logs when SMS Dynamic Volume Count (DVC) function is used to allocate or extend a data set, as shown in Example 1-2.
Example 1-2 New message IGD17296I
IGD17296I DYNAMIC VOLUME COUNT (DVC=nn) WAS USED TO {ALLOCATE|EXTEND}
DATA SET dsn
DVC is a field in the data class that defines the maximum number of volumes that data set can span and is used during the allocation or extend processing if the specified volume count is not sufficient. This new message allows the user to take preventive actions for potential space failures.
1.4 User-defined ACS read-only variable
New user-defined ACS read-only variables for use with ACS routines were introduced. This functionality allows you to specify unique values for your own use. They are similar to how systems symbols are defined and can be used to assign proper constructs without a need to modify the ACS routines.
The new USER_ACSVAR parameter is optional and can be specified in your Parmlib member IGDSMSxx. The new parameter has three positional values. Each value is a user-defined, eight-character string, as shown in the following example:
USER_ACSVAR(value1,value2,value3)
In addition to user-defined values, you can also use any symbols that are defined on IEASYMxx member on your environment. If you do not define USER_ACSVAR on your IGDSMSxx member, the default values are set to blank.
The ACS routines can reference each positional value as &USER_ACSVAR(1), &USER_ACSVAR(2), or &USER_ACSVAR(3).
The values for variables are saved when SMS is started. During ACS processing, the variables are passed to the ACS routines in the form of a new ACS read-only variable. All ACS routines can access the new variables.
The value can be altered with SETSMS command, as shown in the following example:
SETSMS USER_ACSVAR(value1,value2,value3)
When setting USER_ACSVAR via SETSMS command, you can use a single dash (-) to keep current values that you do not want to change, as shown in the following example:
SETSMS USER_ACSVAR(-,-,PROD)
If any positional value is not specified in the command, it is set to blank. The following examples show setting the first, second, and third variables to blank:
•SETSMS USER_ACSVAR(,-,PROD)
•SETSMS USER_ACSVAR(&SYSCLONE,,TEST)
•SETSMS USER_ACSVAR(&SYSNAME,-)
Any combination of dash, blank, user values, or system symbols are allowed.
Example 1-3 uses USER_ACSVAR, which includes SYSPLEX name values to define the correct DATA CLASS to be assigned on ACS routines.
Example 1-3 Sample DATACLASS ACS code
PROC DATACLAS /* DATA CLASS ACS ROUTINE */
IF &USER_ACSVAR(1) = ‘PRODPLX' THEN
SET &DATACLAS = ‘PROD_DC’
ELSE
IF &USER_ACSVAR(1) = ‘TESTPLX’ THEN
SET &DATACLAS = ‘TEST_DC’
ELSE
WRITE ‘***** UNEXPECTED VALUE FOR USER_ACSVAR’
EXIT CODE(0)
END /* END DATA CLASS ROUTINE */
|
Note: To check the USER_ACSVAR content, you can issue a D SMS,OPTIONS. Use of the WRITE command on ACS routines displays the first value only.
|
Because new variables are defined on IGDSMSxx and ACS routines, systems that share SMS Control Data Set (CDS) should not start using USER_ACSVAR until all LPARs are running z/OS V2.2.
1.5 SMS RAS enhancements
As in previous releases, DFSMS in z/OS V2.2 continues to provide RAS enhancements.
1.5.1 New information console message
DFSMS serializes access to SMS control data sets, ACDS, and COMMDS, by issuing a RESERVE with the resource name IGDCDSXS.
The SMS resource name, IGDCDSXS, must be placed in the GRS RESERVE conversion RNL as a generic entry so it can be converted to the global ENQ. This configuration minimizes delays that can occur because of contention for resources and prevents potential deadlocks.
In z/OS V2.2, if IGDCDSXS is not specified in the GRS RESERVE conversion RNL, SMS issues a new informational message (IGD06041I) to the console, as shown in Example 1-4.
Example 1-4 New message IGD06041I
IGD06041I SMS RESOURCE NAME IGDCDSXS IS NOT FOUND IN GRS RESERVE CONVERSION RNL. RETURN CODE retcode REASON CODE rsncode
1.5.2 Enhance SELECT/DESELECT command
The commands SELECT/DESELECT, are used to specify or delete one or more events or services that SMS is to trace.
Before z/OS V2.2, the SELECT/DESELECT command cannot have more than two lines in IGDSMSxx PARMLIB member. In z/OS V2.2, SMS provides support to have more than two lines in the SELECT/DESELECT command for better serviceability.
|
Migration and coexistence considerations: If you share IGDSMSxx PARMLIB member, ensure that all systems are on z/OS 2.2 before this enhancement is used.
|
1.5.3 Including data set name and storage name in ACS messages
In previous releases, SMS issued ACS messages IGD01012I and IGD01015I when data set allocation failed, as shown in Example 1-5.
Example 1-5 IGD01012I and IDG0105I Messages
IGD01012I DATA SET ALLOCATION REQUEST FAILED - THE ACS STORAGE GROUP ROUTINE ASSIGNED A NON-TEMPORARY OR VSAM DATA SET TO A STORAGE GROUP WHICH IS NOT OF TYPE POOL
IGD01015I DATA SET ALLOCATION REQUEST FAILED - THE ACS STORAGE GROUP ROUTINE ASSIGNED A DSNTYPE=type
DATA SET TO A NON POOL TYPE STORAGE GROUP
[CANDIDATE STORAGE GROUP(S): sg1, sg2,...]
In z/OS V2.2, these messages are enhanced to include the data set name and the storage group name for problem diagnosis.
SMS trace entries that are related to these events are also enhanced.
1.5.4 Display Storage Groups in IGD17800I Message
Previous releases of SMS issued message IGD17800I when the specified volumes for a guaranteed space request cannot be found in the eligible storage group list. The storage groups that are searched by SMS is not externalized to the user.
The message IGD17800I is enhanced to display the storage groups that are searched. The new message format is shown in Example 1-6.
Example 1-6 IGD17800I Message
IGD17800I {DATA CLASS dcname| MANAGEMENT CLASS mcname| STORAGE CLASS scname|
STORAGE GROUP sgname|VOLUME volser}
DEFINITION NOT FOUND FOR DATA SET dsname
1.5.5 Externalizing message IGD17364I to hardcopy log
The RETENTION LIMIT value in the Management Class limits the use of a retention period and expiration date. Data sets that are assigned with a RETENTION LIMIT value of zero days that are specified in their Management Class are immediately expired.
Before z/OS V2.2, job logs had to be reviewed to find message IGD17364I to identify which data sets expired for this reason.
This new functionality also externalizes IGD17364I to the hardcopy log. By using this function, the expired data sets can be identified by searching for the IGD17364I messages in the hardcopy log, as shown in Example 1-7.
Example 1-7 IGD173264I Message
IGD17364I DATA SET dsname NOT AUTHORIZED TO EXPIRATION DATE SPECIFIED EXPIRATION DATE RESET TO MAXIMUM ALLOWED yyddd
1.5.6 Storage Group Space alert messages
In previous releases, SMS VTOC Data Set Services (VDSS) issued message IGD17380I to notify a user that the cumulative space that was allocated on the selected storage group exceeded the high allocation threshold.
It might be better to change the alert based on a higher or lower value thresholds to capture more meaningful alerts. DFSMS V2.2 includes new alert thresholds for pool storage groups. These new alerts allows users to have more time to react to storage group space shortage conditions and helps to identify when you must change a storage group’s space management settings or add volumes to a storage group.
The new threshold attributes in the storage group panel to define thresholds are shown in Example 1-8.
Example 1-8 New attributes in Storage Group Display
POOL STORAGE GROUP DISPLAY Page 2 of 2
Command ===>
CDS Name . . . . . : SYS1.STPPLEX.SCDS
Storage Group Name : OPENMVS
Dump Class . . . . . . . . . . . . . . . :
Dump Class . . . . . . . . . . . . . . . :
Dump Class . . . . . . . . . . . . . . . :
Allocation/Migration Threshold - High . : 85
Low . . : 1
Alloc/Migr Threshold Track-Managed - High: 85
Low :
Total Space Alert Threshold % . . . . . :
Track-Managed Space Alert Threshold % . :
Guaranteed Backup Frequency . . . . . . :
BreakPointValue . . . . . . . . . . . . :
Processing Priority . . . . . . . . . . : 50
Use UP Command to View previous Page;
Use HELP Command for Help; Use END Command to Exit.
When no threshold value is specified, it is set to zero and no alert messages is issued. However, when the alert threshold is reached, the new alert messages IGD400I and IGD401I are issued to the console, as shown in the Example 1-9.
Example 1-9 IGD400I and IGD401I alert messages
IGD400I TOTAL SPACE ALERT ON STORAGE GROUP (sgname) CURRENT USAGE (xx%), ALERT THRESHOLD (yy%)
IGD401I TRACK-MANAGED SPACE ALERT ON STORAGE GROUP (sgname)CURRENT USAGE (xx%), ALERT THRESHOLD (yy%)
To prevent the alert messages being issued too frequently, the messages are issued at an incremental interval. The calculated space usage includes “online and enable” volumes only and occurs when the following conditions are present:
•A space change occurs
•Varies the online or offline volume of a pool storage group
•Disables or enables an online volume of a pool storage group
|
Note: The IGD401I alert is issued only for the pool storage group that contains one or more EAV volumes.
|
The IGD002I message includes new information about total and track-managed space for each storage group, as shown in Example 1-10.
Example 1-10 DISPLAY SMS,SG(stgname)
COMMAND INPUT ===> SCROLL ===> PAGE
RESPONSE=SC74
IGD002I 15:30:43 DISPLAY SMS 108
STORGRP TYPE SYSTEM= 1 2 3 4 5
OPENMVS POOL + + + + +
SPACE INFORMATION:
TOTAL SPACE = 16240 MB USAGE% = 83 ALERT% = 80
TRACK-MANAGED SPACE = 16240 MB USAGE% = 83 ALERT% = 80
***************************** LEGEND *****************************
. THE STORAGE GROUP OR VOLUME IS NOT DEFINED TO THE SYSTEM
+ THE STORAGE GROUP OR VOLUME IS ENABLED
- THE STORAGE GROUP OR VOLUME IS DISABLED
* THE STORAGE GROUP OR VOLUME IS QUIESCED
D THE STORAGE GROUP OR VOLUME IS DISABLED FOR NEW ALLOCATIONS ONLY
Q THE STORAGE GROUP OR VOLUME IS QUIESCED FOR NEW ALLOCATIONS ONLY
> THE VOLSER IN UCB IS DIFFERENT FROM THE VOLSER IN CONFIGURATION
SYSTEM 1 = PLEX75 SYSTEM 2 = SC72 SYSTEM 3 = SC73
SYSTEM 4 = SC74 SYSTEM 5 = SC75
In addition, a new keyword, ALERT, allows the message IGD002I to display all of the storage groups that reached one of their alert thresholds. When no storage groups reach the threshold, a new version of the IGD004I message is issued, as shown in Example 1-11.
Example 1-11 New version of IGD004I
IGD004I NO STORAGE GROUPS HAVE REACHED THEIR ALERT THRESHOLDS
|
Note: After an activation of a new configuration, the DISPLAY SMS,SG command might show “UPDATE STILL IN PROGRESS” in some of the storage group space information. Run the V SMS,{STORGRP(storgrp)|SG(storgrp)|VOLUME(volser)|VOL(volser)},{SPACE|S} command to force the space information to be updated for the storage group.
|
1.6 SMF VTOC audit log
The VTOC consists of Data Set Control Blocks (DSCBs) that describe the data sets that are on a volume. The life of a DSCB is managed by DFSMS software. However, other software can also update a DSCB.
Before z/OS V2R2, vendor’s software updates were not recorded in an audit log.
1.6.1 Changes in z/OS V2R2
In z/OS V2.2, the audit logging of VTOC I/O is improved. The logging is done with a new SMF42 Subtype 27 record that captures updates to the VTOC for IBM and vendor-built channel programs.
When a DSCB is written, the following information is recorded:
•Date and time
•System ID, Job Name, Job number, Step name, and Product name
•User Security Token (mapped by ICHRUTKN)
•Activity (from IOBEUSER in IOB Extension):
– Dxxx: DFSMS Activity
– DCVF: CVAFDIR
– DCRE, DREN: Data set create and rename
– DEXT, DPAR: Data set extend and partial release
– DDEL: Data set scratch (read before erase)
– DFRG, DCON: DFSMSdss defrag and consolidate
– DDMP, DRST: DFSMSdss dump and restore
– IOBE: IOBE not provided
– USER: IOBEUSER not specified
•Volume Serial and Device ID (UCB Channel number)
•Seek and Search ID (CCCC HHHH R)
•Caller’s PSW following EXCP SAN Volume Controller
•Device is Reserved flag
•DSCB Key and Data field (140 bytes)
To disable VTOC audit logging, you can use the NOTYPE keyword in parmlib member SMFPRMxx, as shown in Example 1-12.
Example 1-12 Disable VTOC audit logging
NOTYPE(42(27))
EXCP can detect the following writes to the VTOC:
•CKD and IBM ECKD™ channel programs
•DADSM/CVAF
•DSS Defrag/Consolidate, Copy/Restore/Dump
•Vendor channel programs
•XDAP macro instruction (adds support for IOB Extension block)
•SuperZAP (AMASPZAP service)
The following writes are not logged:
•System Resident volume
•Temporary DASD data sets
•I/O to an offline volume
•Updates to DSCB FMT 1, 5, and 7; second DSCB written in channel program
•Use the IOBUSER field in the Input/Output Block (IOB) Extension to Update the VTOC for programs that builds its own EXCP channel program. This field is saved in the SMF 42 subtype 27 record, as shown in Figure 1-1 and Figure 1-2.
Figure 1-1 VTOC SMF 42 subtype 27 example: VTOC Writer Not Identified
Figure 1-2 TOC SMF 42 subtype 27 example: DADSM Create Data Set
1.7 Open/Close/End of Volume
This section provides detailed information about Open/Close/End of Volume enhancements.
1.7.1 Tape performance and recovery
To keep data synchronized between cache and tape, the drive cache must be synchronized with the tape medium.
When a multi-file synchronization fails, all files must be rewritten because there is no way to determine what files were safely written to the tape medium.
In z/OS v2R2, it is possible to specify how many files should be written to tape volumes by a specific job before a synchronization occurs and determine the specific compromised files if there is a synchronization failure.
These enhancements can improve performance by avoiding the overhead and time that is used by unnecessary synchronizations. This enhancement minimizes the number of synchronizations that are performed to the optimum number and improves recovery by providing a means to determining the specific compromised files if there is a synchronize failure.
The new keyword, SYNC=(NUMFILES,’nnn’), must be set in DCBE macro to specify how many files must be written to tape volumes.
The keyword accepts a value of 1 - 32000 that is stored in the new DCBENMFL field. Up to ‘nnn’ consecutive files can be written that specify PASS RETAIN or CLOSE LEAVE before an explicit channel program is written, as shown in Figure 1-13.
Example 1-13 New keyword SYNC
DCBAD DCB DDNAME=DD1,DSORG=PS,MACRF=PM,BLKSIZE=80,RECFM=F,DCBE=DCBEB
DCBEB DCBE RMODE31=NONE,SYNC=(NUMFILES,100)
All data from those files, including file boundaries (tape marks), is buffered in the device cache. After ‘nnn’ files are written, a single explicit synchronization occurs.
If the synchronization fails, the message IEC999I is written to the system and job logs. The job then abends, as shown in Example 1-14.
Example 1-14 Message IEC999I
IEC999I jobname,stepname,volser LOST BLOCKS START: FILE ‘n’
The name of next data set to rewrite can be found in IEC205I message or in the abend message.
1.7.2 Converting tape installation exits
The open, close, and end-of-volume (EOV) tape management exits allow tape management systems to avoid changing system control blocks or issuing channel programs against tapes to maintain a tape inventory.
During opening, processing, and closing a tape data set, the system calls the File Validation, File Start on volume, and File End on volume. Open or EOV calls the file validation exit for each volume, regardless of whether it was mounted or verified.
Many conditions affect whether various exits are called and their sequence. For example, during a call to open or EOV, the following sequence is typical:
•File end on volume exit (if EOV)
•Volume mount exit for volume verification (if volume was not mounted and verified)
•Volume mount exit for volume security (if volume was not mounted and verified)
•File validate exit (if labels exist)
•Volume mount exit for volume write function (if the tape has standard labels, the user is writing and the file is the first file on the volume)
•File start on volume exit
In z/OS V2R2, the Installation Tape Exits were converted to be dynamic. Now, an initial program load (IPL) is not necessary to manage changes with Tape Exits and multiple exit routines can be associated with each exit.
Table 1-1 shows the dynamic exit names, and their respective default exit routines.
Table 1-1 Dynamic exit names and default exit routines
|
Exit Name
|
Default Exit Routine
|
|
OCE_VOLUMEMOUNT
|
IFG019VM
|
|
OCE_FILESTART
|
IFG019FS
|
|
OCE_FILEVALIDATE
|
IFG019FV
|
|
OCE_FILEEND
|
IFG055FE
|
|
OCE_LABELANOMALY
|
IFG019LA
|
When multiple exits are associated, the order in which they are called is not defined unless the options FIRST or LAST are used. The parameter list can be changed by any exit routine, and, in all cases, the parameter list contains last changes from the last called exit routine.
Examples the use multiples exits routines that are defined in PROGxx PARMLIB member are shown in Example 1-15.
Example 1-15 Multiple exits routines
EXIT ADD
EXITNAME(OCE_VOLUMEMOUNT)
MODNAME(MYEXIT1)
STATE(ACTIVE)
DSNAME(MY.PDS)
FIRST
EXIT ADD
EX(OCE_FILESTART)
MOD(MYEXIT2)
LAST
EXIT DELETE
EX(OCE_FILEEND)
MOD(IFG055FE)
Also, if an exit routine ABENDs, it is made inactive immediately and stays inactive until it is activated manually or the system is loaded.
The following commands are available:
•To display Open/Close/EOV tape installation exits, use the following command:
D PROG,EXIT,EXITNAME=OCE_*
•To display diagnostic data, including exit routines for Volume Mount, use the following command:
D PROG,EXIT,EX=OCE_VOLUMEMOUNT,DIAG
•To add MYEXIT1 exit routine in MY.PDSE data set to File Start exit, use the following command:
SETPROG EXIT,ADD,EX=OCE_FILESTART,MODNAME=MYEXIT1,DSN=MY.PDSE
•To add and make MYEXIT2 exit routine to be called the first every time after File End exit gets control, use the following command:
SETPROG EXIT,ADD,EX=OCE_FILEEND,MOD=MYEXIT2,FIRST
•To make MYEXIT3 exit routine inactive for File Validate exit, use the following command:
SETPROG EXIT,MODIFY,EX=OCE_FILEVALIDATE,MOD=MYEXIT3,STATE=INACTIVE
•To delete MYEXIT4 exit routine from File End exit, use the following command:
SETPROG EXIT,DELETE,EX=OCE_FILEEND,MODNAME=MYEXIT4
1.7.3 DEVSUPxx enhancements
Device Support Options (DEVSUPxx) specifies the installation default for device support options. DEVSUPxx is processed during the NIP phase of IPL. After IPL, customers can use system command SET DEVSUP=XX to activate the DEVSUP changes.
Multiple DEVSUP member support
In previous releases, the command SET DEVSUP MVS™ and the keyword DEVSUP in IEASYSxx PARMLIB member support single value only. z/OS V2.1 includes an enhanced Multiple Virtual Storage (MVS) command and keyword to support multiple values. The enhancement is shown in Example 1-16.
Example 1-16 DEVSUP multiple values
SET DEVSUP=(xx,yy,zz...)
DEVSUP=(xx,yy,zz...)
Missing DEVSUP member message
When SET DEVSUP=xx command was issued but the DEVSUPxx member did not exist, the following message was issued:
IEE536I DEVSUP VALUE xx NOW IN EFFECT.
In z/OS V2R2, this message is not issued if DEVSUPxx member does not exist. In addition, IEE538I message is displayed to alert the user that the required DEVSUPxx was not found on parmlib.
Continued processing after keyword error
In z/OS V2R2, DEVSUP parameter processing does not stop after a keyword error is encountered. Instead, it issues the message IEA25IE, which was enhanced to display the statement in error, and the DEVSUPxx member it is coded, as shown in Example 1-17.
Example 1-17 IEA251E message
IEA251E DEVSUP8A: NON_VSAM_XTIOT PARAMETER 'TES' NOT VALID.
IEA252E DEVSUP8A: INVALID SYNTAX ON LINE 0002. MEMBER PROCESSING CONTINUES.
Preserve keyword values
In previous releases, there is a subset of DEVSUPxx keywords that were reset to their default values whenever a member was processed, unless the values were explicitly set in the member. However, this process created an inconsistency in how all keywords are processed.
In z/OS V2R2, the current values of all keywords are preserved when a DEVSUPxx member is processed, unless the member explicitly specifies new values.
1.7.4 Adding JOBID and SYSPLEXID SMF 14 and 15 enhancements
SMF writes a type 14 or 15 record whenever a data set is closed or processed by EOV. These records can be used to gather information about the user that is accessing the data set, date and time, and type of access, and others.
Usage and invocation
In z/OS V2.2, the JCTJOBID, JES2 job identifier, and SYSPLEXID are added to SMF 14 and 15 to give more information about where a job ran. The new field of SMF 14 and 15 records are automatically included when they are requested.
1.7.5 Including above the line CSECTs in OCE in-core module table
The Open, Close, and End-of-volume (OCE) functions maintains an in-core module table with the following entries:
•CSECT name
•LPA address
•PTF level
Currently, this table does not contain any of 12 CSECTs of IFG019RB module.
In z/OS V2R2, these CSECTs of IFG019RB module are included in an in-core module table above the line, which eliminates requests from Level 2 for PTF’s level.
1.7.6 Eliminating A13-18 while ensuring correct mount
Before z/OS V2R2, the ABEND A13 RC=18 occurred in the following situations:
•When an EOV1 label is read on the last SL or AL tape volume while forward spacing to the wanted file or just before the wanted file. The following conditions are possible:
– If opening to the end of the file, it cannot be treated as the end of the data set because it was for a previous file sequence number. Probable user error.
– If the user is trying to extend a data set that abended during EOV, it is necessary to specify a volume count on the DISP=MOD DD statement. This volume count must exceed the number of known volumes for the data set.
•When there are multiple DDs for tape data sets to be created in the same step. The first DD contains a specific volser and the subsequent DDs specify a VOLREF back to the first DD.
•When one of the data sets being written overflows to another volume, that volume is not known to the subsequent DDs in the job step.
In z/OS V2R2, this abend was eliminated. This new functionality enables the use of multiple DD statements, which passes the correct volume to the next DD statement and avoids errors. As shown in Example 1-18, DD1 spills to scratch volume 222222. When DD2 is processed, open replaces 111111 with 222222 in the JFCB.
Example 1-18 Sample JCL
//JOB ...
//STEP1 EXEC ...
//DD1 DD DSN=DATASET1,
// DISP=(NEW,PASS,KEEP),
// VOL=SER=111111,
// UNIT=920,
// LABEL=(1,SL)
//DD2 DD DSN=DATASET2,
// DISP=(NEW,PASS,KEEP),
// VOL=REF=*.STEP1.DD1,
// UNIT=920,
// LABEL=(2,SL)
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.