z/OS 1.9 - 1.11 can cause an ABEND S338 when having installed the PTF to support e.g UA51982 or UA51982.
This affects the software component RA/7. RA/7 must be APF defined
To circumvent this problem an installation has to perform the following tasks until an updated version is on the net:
1. Exits Definitionen in SMFPRMxx member with the SMFDLEXIT and SMFDPEXIT keywords
- USER2(IRRADU00)
- USER3(IRRADU86)
- USER2(RA7$RW20)
- USER3(RA7$RW30)
- USER2(RA7$IW20)
- USER3(RA7$IW30)
- USER2(RA7$RW81)
- USER3(RA7$RW82)
Syntax sample:
SMFDLEXIT( USER1( exit1, exit2, ... ) | NOUSER1 ,
USER2( exit1, exit2, ... ) | NOUSER2 ,
USER3( exit1, exit2, ... ) | NOUSER3 )
SMFDPEXIT( USER1( exit1, exit2, ... ) | NOUSER1 ,
USER2( exit1, exit2, ... ) | NOUSER2 ,
USER3( exit1, exit2, ... ) | NOUSER3 )
Default settings are:
SMFDLEXIT(USER2(IRRADU00),USER3(IRRADU86))
SMFDPEXIT(USER2(IRRADU00),USER3(IRRADU86))
2. LINK/EDIT the following modules RA/7 Version 3.5.1 and below ONLY!
//LKED EXEC PGM=IEWL,PARM=('XREF,LIST,MAP,AC=1')
//SYSLIB DD DSN=RA7350.LINKLIB, DISP=SHR
//SYSUT1 DD DSN=&&SYSUT1,UNIT=VIO,SPACE=(CYL,(5,3))
//SYSPRINT DD SYSOUT=*,DCB=(RECFM=FB,LRECL=121,BLKSIZE=1210)
//SYSLIN DD DDNAME=SYSIN
//SYSLMOD DD DSN=RA7350.LINKLIB,DISP=SHR
//LKED.SYSIN DD *
INCLUDE SYSLMOD(RA7$RW00)
SETCODE AC(0)
ENTRY RA7$RW00
ORDER RA7$RW00(P)
NAME RA7$RW00(R)
INCLUDE SYSLMOD(RA7$RW10)
SETCODE AC(0)
ENTRY RA7$RW10
ORDER RA7$RW10(P)
NAME RA7$RW10(R)
INCLUDE SYSLMOD(RA7$RW80)
SETCODE AC(0)
ENTRY RA7$RW80
ORDER RA7$RW80(P)
NAME RA7$RW80(R)
INCLUDE SYSLMOD(RA7$IW10)
SETCODE AC(0)
ENTRY RA7$IW10
ORDER RA7$IW10(P)
NAME RA7$IW10(R)
INCLUDE SYSLMOD(RA7$IW50)
SETCODE AC(0)
ENTRY RA7$IW50
ORDER RA7$IW50(P)
NAME RA7$IW50(R)
//
3. Update IKJTSOxx
Make IFASMFDP and IFASMFDL run in an authorized environment.
Running the SMF dump programs via JCL preserves the
APF-authorization assigned to the SMF dump programs and
nothing needs to be done. If IFASMFDP or IFASMFDL is being
executed under TSO then it may lose its authorization and action
needs to be taken.
For the TSO environment this can be fixed by adding IFASMFDP and
IFASMFDL to the AUTHPGM section of IKJTSOxx PARMLIB member when
IFASMFDP or IFASMFDL is being invoked via a TSO CALL command. If
LINKMVS or ATTCHMVS are used to invoke IFASMFDP or IFASMFDL
then they need to be changed to use the TSO CALL command as well
as have the AUTHPGM section of IKJTSOxx updated.
In addition the following modules must be define to AUTHPGM for RA/7:
- RA7$IW10
++ HOLD(UA51982) SYS FMID(HBB7760) REASON(EXIT) DATE(10020)
COMMENT
(****************************************************************
* FUNCTION AFFECTED: System Management Facility (OA29894) *
* (SMF) *
****************************************************************
* DESCRIPTION : Installation Notes *
****************************************************************
* TIMING : Post-Apply *
****************************************************************
All exits used by the IFASMFDP and IFASMFDL programs should be
identified and added to the SMFPRMxx member with the SMFDLEXIT
or SMFDPEXIT keywords, respectively.).
++ HOLD(UA51982) SYS FMID(HBB7760) REASON(DOC) DATE(10020)
COMMENT
(****************************************************************
* FUNCTION AFFECTED: System Management Facility (OA29894) *
* (SMF) *
****************************************************************
* DESCRIPTION : Documentation updates *
****************************************************************
* TIMING : Post-apply *
****************************************************************
The MVS System Managment Facilities (SMF) manual will
be updated as follows:
ORDER NO - SA22-7630-00
Book Title- MVS System Management Facilities (SMF)
+--- LOCATION IN PUBLICATION ---------------------------+
! !
! In: Chapter: 3 Using the SMF Dump Programs !
! Section: 3.1.1 Specifying parameters for the !
! SMF log stream dump program !
! !
+-------------------------------------------------------+
3. USERx parameters: The name fields in
USER1, USER2, or USER3 specify the name of
a load module that the SMF log stream dump
program loads and calls at the indicated
times. You can either link-edit each exit
into a library in LINKLIST (but do not use
the AC=1 attribute) or use a //STEPLIB DD
! card. All exits specified must be defined
! to the system in the SMFPRMxx member with
! the SMFDLEXIT parameter.
+--- LOCATION IN PUBLICATION ---------------------------+
! !
! In: Chapter: 3 Using the SMF Dump Programs !
! Section: 3.2.1 Specifying parameters for the !
! SMF data set dump program !
! !
+-------------------------------------------------------+
Note: The name field in USER1, USER2, or
USER3 specifies the name of a load
module that the SMF data set dump
program loads and calls at the
indicated times. You can either
link-edit each exit into an
APF-authorized library in LINKLIST
(but do not use the AC=1 attribute)
! or use a //STEPLIB DD card. All exits
! specified must be defined
! to the system in the SMFPRMxx member with
! the SMFDPEXIT parameter.
+--- LOCATION IN PUBLICATION ---------------------------+
! !
! In: Chapter: 4 Customizing SMF !
! Section: 4.1.xx SMFDLEXIT and SMFDPEXIT - !
! Specifying dump program exits !
! !
+-------------------------------------------------------+
! 4.1.xx SMFDLEXIT and SMFDPEXIT -
! Specifying dump program exits
!
! To allow user exits to be called by the SMF dump programs,
! they must be pre-defined to the system using these keywords.
! The SMFDLEXIT allows exits to be specified for the IFASMFDL
! program and SMFDPEXIT allows exits to be specified for the
! IFASMFDP program.
!
! Both keywords have the same suboptions, USER1, USER2 and
! USER3. They allow multiple exits to be specified for
! each user exit point in the respective dump program.
! Once an exit is specified via USER1, USER2 or USER3, it
! will remain in effect until another a SETSMF is done for
! either USER1, USER2 or USER3 or a SET SMF is done.
!
! For example, to have user exit SAMPEXIT available as
! a USER2 exit for IFASMFDP one would code the following
! in the active SMFPRMxx member:
!
! SMFDPEXIT(USER2(SAMPEXIT))
!
! If a SETSMF is done with the following parameters:
!
! SMFDPEXIT(USER1(SAMPEXT2))
!
! This would only affect USER1, however the USER2 previously
! specified would remain in effect.
!
The MVS System Messages manual will be updated as follows:
ORDER NO - SA22-7638-00
Book Title- MVS System Messages, Vol 8 (IEF-IGD)
+--- LOCATION IN PUBLICATION ---------------------------+
! !
! In: Chapter: 9.0 IFA messages !
! Section: 9.xx IFA840I !
! !
+-------------------------------------------------------+
! IFA840I USER EXIT xxxxxxxx NOT REGISTERED WITH SYSTEM
!
! Explanation: An exit specified for IFASMFDL or IFASMFDP
! via the USER1, USER2 or USER3 parameters
! is not registered with the system by way
! of the SMFPRMxx member.
!
! In the message text:
!
! xxxxx The name of the user exit
!
! System Action: IFASMFDL or IFASMFDP stops processing and
! returns an x'08'
!
! Operator Response: None.
!
! System Programmer Response: If this is an exit which is
! required for IFASMFDL or
! IFASMFDP processing then
! define the exit name to the
! system in the SMFPRMxx member
! with either the SMFDLEXIT or
! SMFDPEXIT keywords.
!
! Source: System Management Facilities (SMF)
!
! Detecting Module: IFASMFDL, IFASMFDP
!
! Routing Code: 11
!
! Descriptor Code: -
!
The MVS Initialization and Tuning manual will be updated
as followed:
ORDER NO - SA22-7592-00
Book Title- MVS Initialization and Tuning Reference
+--- LOCATION IN PUBLICATION ---------------------------+
! !
! In: Chapter: 70.0 SMFPRMxx !
! Section: 70.0 SMFPRMxx !
! !
+-------------------------------------------------------+
You can use SMFPRMxx parameters to:
...
. Specify whether only registration data and not usage data is
to be recorded when using the IFAUSAGE macro.
! . Specify valid user exits for the IFASMFDP
! and IFASMFDL programs.
+--- LOCATION IN PUBLICATION ---------------------------+
! !
! In: Chapter: 70.0 SMFPRMxx !
! Section: 70.6 Syntax format of SMFPRMxx !
! !
+-------------------------------------------------------+
The following is the syntax format of SMFPRMxx:
...
! SMFDLEXIT({ USER1({exit1, exit2, ...}) ! NOUSER1 },
! { USER2({exit1, exit2, ...}) ! NOUSER2 },
! { USER3({exit1, exit2, ...}) ! NOUSER3 })
! SMFDPEXIT({ USER1({exit1, exit2, ...}) ! NOUSER1 },
! { USER2({exit1, exit2, ...}) ! NOUSER2 },
! { USER3({exit1, exit2, ...}) ! NOUSER3 })
!
+--- LOCATION IN PUBLICATION ---------------------------+
! !
! In: Chapter: 70.0 SMFPRMxx !
! Section: 70.9 Parameters for SMFPRMxx !
! !
+-------------------------------------------------------+
! SMFDLEXIT / SMFDPEXIT
!
! This keyword allows for valid exits to be specified to
! either the IFASMFDL or IFASMFDP program, respectively.
! Using the USER1, USER2 or USER3 parameters a number of
! valid exits can be specified. If there are no valid
! exits for a given exit point then the NOUSER1, NOUSER2
! or NOUSER3 keyword can be used.
!
! Any combination of subparameters are valid for both the
! SMFDLEXIT and SMFDPEXIT keywords.
!
! Default: SMFDLEXIT(USER2(IRRADU00),USER3(IRRADU86))
! SMFDPEXIT(USER2(IRRADU00),USER3(IRRADU86))
!
The MVS Diagnosis: Reference will be updated as follows:
ORDER NO - GA22-7588-00
Book Title- MVS Diagnosis: Reference
+--- LOCATION IN PUBLICATION ---------------------------+
! !
! In: Chapter: 1.0 System Reference !
! Section: 1.6.2.1 ENQ/DEQ summary !
! !
+-------------------------------------------------------+
1.6.2.1 ENQ/DEQ summary
The following table shows major and minor ENQ/DEQ names and
the resources at the SYSTEM or SYSTEMS level.
Major Minor Resource - Using modules
...
! SYSZSMFD ExitTable Used by IFASMFDL, IFASMFDP and
! SET SMF=xx/SETSMF processing to
! serialize exit tables built
! for exit validation.
Für UA53256 gibt es auch noch eine ACTION:
ACTION:
****************************************************************
* FUNCTION AFFECTED: System Management Facility (OA32258) *
* (SMF) *
****************************************************************
* DESCRIPTION : Installation Notes *
****************************************************************
* TIMING : Post-Apply *
****************************************************************
Make IFASMFDP and IFASMFDL run in an authorized environment.
Running the SMF dump programs via JCL preserves the
APF-authorization assigned to the SMF dump programs and
nothing needs to be done. If IFASMFDP or IFASMFDL is being
executed under TSO then it may lose its authorization and action
needs to be taken.
For the TSO environment this can be fixed by adding IFASMFDP and
IFASMFDL to the AUTHPGM section of IKJTSOxx PARMLIB member when
IFASMFDP or IFASMFDL is being invoked via a TSO CALL command. If
LINKMVS or ATTCHMVS are used to invoke IFASMFDP or IFASMFDL
then they need to be changed to use the TSO CALL command as well
as have the AUTHPGM section of IKJTSOxx updated.