SMFPRMxx z/OS 1.9 and above
For z/OS 2.x - due to the IBM exits IRRADU00/86 (one module) - RA/7 ONLINE ISPF will abend with an S684. Get a copy of this IBM EXIT in SYS1.LINKLIB from e.g. z/OS 1.13 or earlier and create an APF LINKLIB containing just this module. STEPLIB/CONCAT it to your RA7.LINKLIB under ISPF ONLY to bypass this problem until a solution is provided by IBM.
Please refer to the supplied users guide manual as you must install a user SVC. The user SVC is required for ISPF and the REXX interface.
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))
1. RA2002 Exits definitions in SMFPRMxx member with the SMFDLEXIT and SMFDPEXIT keywords
- USER2(SMF$XT20)
- USER3(SMF$XT21)
- USER2(SMF$XT30)
- USER3(SMF$XT31)
- USER2(SMF$XT50)
- USER3(SMF$XT51)
- USER2(SMF$XT60)
- USER3(SMF$XT61)
2. RA/7 Exits definitions 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)
3. RA/7 ALL Exits definitions in SMFPRMxx member with the SMFDLEXIT and SMFDPEXIT keywords
SMFDLEXIT(USER2(IRRADU00,
SMF$XT20,
SMF$XT30,
SMF$XT50,
SMF$XT60,
RA7$RW20,
RA7$IW10,
RA7$RW81),
USER3(IRRADU86,
SMF$XT21,
SMF$XT31,
SMF$XT51,
SMF$XT61,
RA7$RW30,
RA7$IW30,
RA7$RW82))
SMFDPEXIT(USER2(IRRADU00,
SMF$XT20,
SMF$XT30,
SMF$XT50,
SMF$XT60,
RA7$RW20,
RA7$IW10,
RA7$RW81),
USER3(IRRADU86,
SMF$XT21,
SMF$XT31,
SMF$XT51,
SMF$XT61,
RA7$RW30,
RA7$IW30,
RA7$RW82))
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.