Alloc_Routine:
/**********************************************************/
/* DSN is passed as a parm when Alloc_Routine is called */
/**********************************************************/
ARG dsn_name .
DSN_status = SYSDSN(dsn_name)
If DSN_status = "OK"
Then Do
"ALLOC DSN('"dsn_name"') OLD REUSE"
AllocRC = RC
Else Do
"ALLOC DSN('"dsn_name"') NEW CATLG SPACE(CYL,1,1) UNIT(SYSDA)" ,
"LRECL(80) BLKSIZE(0)..."
AllocRC = RC
End
If AllocRC = 0
Then Nop
Else Say "Unable to Allocate DSN("dsn_name"), RC="AllocRC
Return AllocRC
2010年12月20日 星期一
2010年10月19日 星期二
Is There a Way to Dynamically Add PUBLIC/STORAGE Volumes
Are your public (work) volumes SMS managed? If so, then you must initialize the volumes and put the new volsers in the appropriate storage group (look to see if there are any extras in there already - we tend to put non-existant volsers in our storage groups just for this case).
If the work volumes are not SMS managed, then simply initialize them to the appropriate volser, then issue a mount command for each of them similar to:
MOUNT dddd,VOL=(SL,volser),USE=PUBLIC
where "dddd" is the device number and "volser" is the new volser, and you're done. Oh, update the VATLSTnn member to include the new volsers also.
If the work volumes are not SMS managed, then simply initialize them to the appropriate volser, then issue a mount command for each of them similar to:
MOUNT dddd,VOL=(SL,volser),USE=PUBLIC
where "dddd" is the device number and "volser" is the new volser, and you're done. Oh, update the VATLSTnn member to include the new volsers also.
Recatalog IODF
Assuming the IODF volume is shared by both systems, you do use DEFINE RECATALOG. This is how we share the IODF between all our sysplexes and do dynamic activates.
Here is a sample of the job I use to catalog the IODF dsns in the "current" master catalog:
//JS010 EXEC PGM=IDCAMS,REGION=2M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER -
(NAME(SYS1.IODF00.CLUSTER ) -
VOLUMES(SYS019) -
RECATALOG -
LINEAR)
Here is a sample of the job I use to catalog the IODF dsns in the "current" master catalog:
//JS010 EXEC PGM=IDCAMS,REGION=2M
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER -
(NAME(SYS1.IODF00.CLUSTER ) -
VOLUMES(SYS019) -
RECATALOG -
LINEAR)
2010年9月18日 星期六
Taking a DUMP of a specific batch job/STC
This is the procedure for a standard address space dump of a specific batch
job or started task:
1. DUMP COMM=(BATCH JOB ADRESS SPACE DUMP) <= your title for the dump
2. D R,L for WTOR IEE094D SPECIFY OPERAND (S) FOR DUMP COMMAND
3. Reply with xxxx,JOBNAME=(JOBNAME1,JOBNAME2),SDATA=(CSA,RGN,PSA,SQA,LSQA,TRT,SUM),END
4. The system will now take a dump of the address space/spaces.
5. When dump finished (may take a while, 5-10 minutes), it will issue msg
IEA611I to the log saying COMPLETE. This will also give you the dump
dataset name which you can check for the eye catcher title or you can
check the log for previous message IEA794I which says dump captured and
gives title and dataset name.
6. If IEA611I msg says PARTIAL you'll need to rectify any issues and start
again probably.
7. Package up and send off to IBM using standard procedures.
job or started task:
1. DUMP COMM=(BATCH JOB ADRESS SPACE DUMP) <= your title for the dump
2. D R,L for WTOR IEE094D SPECIFY OPERAND (S) FOR DUMP COMMAND
3. Reply with xxxx,JOBNAME=(JOBNAME1,JOBNAME2),SDATA=(CSA,RGN,PSA,SQA,LSQA,TRT,SUM),END
4. The system will now take a dump of the address space/spaces.
5. When dump finished (may take a while, 5-10 minutes), it will issue msg
IEA611I to the log saying COMPLETE. This will also give you the dump
dataset name which you can check for the eye catcher title or you can
check the log for previous message IEA794I which says dump captured and
gives title and dataset name.
6. If IEA611I msg says PARTIAL you'll need to rectify any issues and start
again probably.
7. Package up and send off to IBM using standard procedures.
zFS file How TO
(1) Create and Format a zFS file:
//DEFINE EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=A
//SYSUDUMP DD SYSOUT=a
//AMSDUMP DD SYSOUT=A
//DASD DD DISP=OLD,UNIT=3390,VOL=SER=ZFS001
//SYSIN DD *
DEFINE CLUSTER (NAME(OMVS.ZFS.COMPAT.AGR0001) -
VOLUMES(ZFS001) -
LINEAR -
CYL(10 0) -
SHAREOPTIONS(3))
/*
//ZFSBIT EXEC PGM=IOEAGFMT,REGION=0M,
// PARM=('-aggregate OMVS.ZFS.COMPAT.AGR0001 -compat')
//STDOUT DD SYSOUT=A
//STDERR DD SYSOUT=A
//SYSUDUMP DD SYSOUT=A
//CEEDUMP DD SYSOUT=A
//SYSPRINT DD SYSOUT=A
//*
(2) Growing a zFS Aggregate file:
>> Dataset must have a secondary extent defined and space must exist on the volume to grow into.
>> Size specified on the grow command must be larger thant the current size of the aggregate.
>> You may need to allocate extra blocks for grow to work succesfully as SMS might require some reserved blocks.
>> Size of 0 (zero) grows the agrregate by the size of the secondary allocation.
Example:
zfsadm aggrinfo OMVS.ZFS.COMPAT.AGR0001
| OMVS.ZFS.COMPAT (R/W COMP): 1150 K free out of total 1440
zfsadm grow OMVS.ZFS.COMPAT.AGR0001 1440
| IOEZ00175E Error growing aggregate OMVS.ZFS.COMPAT.AGR0001, error code=121 reason code=EF17606E
zfsadm grow OMVS.ZFS.COMPAT.AGR0001 1441
| IOEZ00173I Aggregate OMVS.ZFS.COMPAT.AGR0001 successfully grown
| OMVS.ZFS.COMPAT.AGR0001 (R/W COMP): 1798 K free out of total 2160
>> Automatically Grow an Agrregate by specifying AGGGROW parameter on mount command……
>> or set default in IOEFSPRM globally.
>> If out-of-space condition occurs Aggregate is automatically grown and I/O re-driven transparently
(3) Adding A volume to an Aggregate:
//STEP01 EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
ALTER OMVS.ZFS.COMPAT.AGR0001.DATA -
ADDVOLUMES(* *)
Adds two volumes to the candidate volume list, selected by SMS. Specify VOLSER if specific volumes
are needed. File must be closed and re-opened before candidates become available for allocation.
UNMOUNT and MOUNT zFS files again to achieve this…. (including any CLONEed files systems!!!)
(4) Backing up a zFS File System with DFDSS:
Backup and Restore of zFS Aggregate
To Backup a zFS file system simply use DFDSS….
//*-----------------------------------------------------------------
//* THIS JOB QUIESCES A ZFS AGGREGATE, DUMPS IT, THEN UNQUIESCES IT.
//*-----------------------------------------------------------------
//DUMP EXEC PGM=ADRDSSU,REGION=4096K
//SYSPRINT DD SYSOUT=*
//SYSABEND DD SYSOUT=*
//OUT DD DSN=hlq.ZFS.BACKUP,
// DISP=(NEW,CATLG,DELETE),SPACE=(CYL,(5,1),RLSE)
//SYSIN DD *
DUMP DATASET(INCLUDE(OMVS.ZFS.COMPAT.AGR0001)) -
CONCURRENT -
OUTDD(OUT)
/*
//
Note: The file systems needs to be attached but not nescessarily mounted.
(5) Restoring a zFS File System with DFDSS:
To Restore the zFS file system….
//*-----------------------------------------------------------------
//* THIS JOB RESTORES A ZFS AGGREGATE.
//*-----------------------------------------------------------------
//ZFSREST EXEC PGM=ADRDSSU,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSABEND DD SYSOUT=*
//INDS DD DISP=SHR,DSN=hlq.ZFS.BACKUP
//SYSIN DD *
RESTORE DATASET(INCLUDE(**)) -
CATALOG -
RENAMEU( -
(OMVS.ZFS.COMPAT.AGR0001, -
OMVS.ZFS.COMPAT.AGR0001.RESTORE) -
) -
WRITECHECK -
INDD(INDS)
>> Once restored the old file will need to be unmounted and then
the new one mounted in it's place….
>> To restore into the original zFS aggregate run the following.
>> File cannot be mounted or attached whilst restore is running
//*---------------------------------------------------
//* THIS JOB RESTORES A ZFS AGGREGATE.
//*---------------------------------------------------
//ZFSREST EXEC PGM=ADRDSSU,REGION=0M
//SYSPRINT DD SYSOUT=*
//SYSABEND DD SYSOUT=*
//INDS DD DISP=SHR,DSN=hlq.ZFS.BACKUP
//SYSIN DD *
RESTORE DATASET(INCLUDE(OMVS.ZFS.COMPAT.AGR0001)) -
CATALOG -
REPLACE -
WRITECHECK -
INDD(INDS)
(6) Mounting zFS File Systems:
Mounting zFS File Systems
To add entries so that the zFS file systems are mounted automatically on the next IPL:
From z/OS 1.3 upwards, zFS file systems can be mounted via BPXPRMxx e.g.
MOUNT FILESYSTEM('OMVS.ZFS.COMPAT.AGR001') TYPE(ZFS)
MOUNTPOINT('/etc/zfs/mntpoint')
Prior to z/OS 1.3 zFS file systems could not be mounted via BPXPRMxx.
To mount via IPL you should place /usr/sbin/mount commands in /etc/rc.
For example:
/usr/sbin/mount -f OMVS.ZFS.COMPAT.AGR001 -t ZFS /etc/zfs/mntpoint
Either command can be entered via TSO or OMVS respectively to mount a file system post IPL.
Usefull Parameters on the MOUNT command:
AGGRFULL(90,5) Issues WTO when Aggregate is 90% full and every 5% after.
AGGRGROW File system can dynamically grow
Examples:
MOUNT FILESYSTEM('OMVS.ZFS.COMPAT.AGR0001') MOUNTPOINT('/etc/zfs/mntpoint')
TYPE(ZFS) MODE(RDWR) PARM('AGGRFULL(90,5)')
/usr/sbin/mount -f OMVS.ZFS.COMPAT.AGR0001 -t ZFS -o 'AGGRFULL(90,5)' /etc/zfs/mntpoint
(7) Determining Free Space in an Aggregate:
Display a Brief summary of aggregate space:
zfsadm aggrinfo
Result:
/:zfsadm aggrinfo
IOEZ00370I A total of 2 aggregates are attached.
OMVS.ZFS.SAMPLE.FILE1 (R/W COMP): 636386 K free out of total 720000
OMVS.ZFS.SAMPLE.FILE2 (R/W COMP): 971840 K free out of total 1080000
Display a Detailed summary of aggregate space:
zfsadm aggrinfo -long
Result:
/:zfsadm aggrinfo -long
IOEZ00370I A total of 2 aggregates are attached.
OMVS.ZFS.SAMPLE.FILE1 (R/W COMP): 636386 K free out of total 720000
version 1.4
79498 free 8k blocks; 402 free 1K fragments
3600 K log file; 48 K filesystem table
112 K bitmap file
OMVS.ZFS.SAMPLE.FILE2 (R/W COMP): 971840 K free out of total 1080000
version 1.4
120639 free 8k blocks; 6728 free 1K fragments
10800 K log file; 56 K filesystem table
160 K bitmap file
Display a Detailed summary of a specific aggregate space:
zfsadm aggrinfo OMVS.ZFS.SAMPLE.FILE1 -long
Result:
/:zfsadm aggrinfo OMVS.ZFS.SAMPLE.FILE1 -long
OMVS.ZFS.SAMPLE.FILE1 (R/W COMP): 636378 K free out of total 720000
version 1.4
79497 free 8k blocks; 402 free 1K fragments
3600 K log file; 48 K filesystem table
112 K bitmap file
Submitting JCL using REXX
The rexx code is as below:
QUEUE "//CPYTAPE1 JOB (),'COPY',CLASS=b,MSGCLASS=a,"
QUEUE "// REGION=0M,NOTIFY=&SYSUID"
QUEUE "//STEP1 EXEC PGM=IEBGENER"
QUEUE "//SYSOUT DD SYSOUT=*"
QUEUE "//SYSPRINT DD SYSOUT=*"
QUEUE "//SYSUT1 DD DSN="DDIN",DISP=SHR"
QUEUE "//SYSUT2 DD DSN="DDIN".NEW,"
QUEUE "// DISP=(NEW,CATLG,DELETE),"
QUEUE "// DATACLAS=MEDIUM,"
QUEUE "// UNIT=CART"
QUEUE "//SYSIN DD *"
"ALLOC F(JCL) SYSOUT WRITER(INTRDR) RECFM(F B) LRECL(80)"
"EXECIO" QUEUED() "DISKW JCL (FINIS"
"FREE F(JCL)"
QUEUE "//CPYTAPE1 JOB (),'COPY',CLASS=b,MSGCLASS=a,"
QUEUE "// REGION=0M,NOTIFY=&SYSUID"
QUEUE "//STEP1 EXEC PGM=IEBGENER"
QUEUE "//SYSOUT DD SYSOUT=*"
QUEUE "//SYSPRINT DD SYSOUT=*"
QUEUE "//SYSUT1 DD DSN="DDIN",DISP=SHR"
QUEUE "//SYSUT2 DD DSN="DDIN".NEW,"
QUEUE "// DISP=(NEW,CATLG,DELETE),"
QUEUE "// DATACLAS=MEDIUM,"
QUEUE "// UNIT=CART"
QUEUE "//SYSIN DD *"
"ALLOC F(JCL) SYSOUT WRITER(INTRDR) RECFM(F B) LRECL(80)"
"EXECIO" QUEUED() "DISKW JCL (FINIS"
"FREE F(JCL)"
2010年9月8日 星期三
DB2 exits
The default DB2 exit routine - Copyright IBM Corporation 2004, 2009. All Rights Reserved.
The default DB2® exit routine at the DSNX@XAC exit point returns a code to the DB2 authorization module indicating that an installation-defined access control authorization exit routine is not available. DB2 then performs native authorization checking and does not attempt to invoke this exit routine again. The default DB2 exit routine called DSNX@XAC is in library prefix.SDSNLOAD. The source code for the default DB2 exit routine is in the DSNXSXAC member of prefix.SDSNSAMP. The DB2 installation process puts the results of the assembly into prefix.SDSNEXIT.
By contrast, the RACF access control module is provided in DSNXRXAC member of prefix.SDSNSAMP and provides access control using a combination of RACF® and DB2 checking. You can easily alter the DB2 installation process by modifying the DSNTIJEX job to assemble the RACF access control module, rather than the default DB2 exit routine.
The default DB2® exit routine at the DSNX@XAC exit point returns a code to the DB2 authorization module indicating that an installation-defined access control authorization exit routine is not available. DB2 then performs native authorization checking and does not attempt to invoke this exit routine again. The default DB2 exit routine called DSNX@XAC is in library prefix.SDSNLOAD. The source code for the default DB2 exit routine is in the DSNXSXAC member of prefix.SDSNSAMP. The DB2 installation process puts the results of the assembly into prefix.SDSNEXIT.
By contrast, the RACF access control module is provided in DSNXRXAC member of prefix.SDSNSAMP and provides access control using a combination of RACF® and DB2 checking. You can easily alter the DB2 installation process by modifying the DSNTIJEX job to assemble the RACF access control module, rather than the default DB2 exit routine.
VTAM exits
- ISTAUCAG - Calculates and records time during which a terminal user or an application program is logged onto an application program
- ISTAUCAT - Validates a logon request to an application program
- ISTEXCVR - Provides ACF/VTAM® with an ordered list of virtual routes for path selection to transmit data through network
- ISTINCDT - User supplies supplementary tables to session-link unformatted system services (USS) table which ACF/VTAM uses to handle command input and message output
- ISTINCLM - User can change IBM-supplied logon mode table which contains parameters representing protocols for telecommunications session or user can supply supplementary tables
- ISTINCNO - User supplies supplementary tables to operation-level USS tables which handle commands from an ACF/VTAM operator and messages to an ACF/VTAM operator
- ISTMGC00 - Communication network management (CNM) table routes unsolicited network service requests to application programs to record and report maintenance statistics
- ISTPUCWC - Virtual route pacing window size calculator specifies limits to data flow through a network to avoid congestion in nodes along a virtual route
- ISTRACON - Module containing constants used to control functions not suitable for modification by operator command or start option
TSO exits
- ADRS exit - Perform additional processing whenever a user selects the ADRS option from the Information Center Facility
- CHSFEXIT - Change default space parameters that VM/PC servers use to dynamically allocate MVS data sets
- ICQAMFX1 - Application manager function pre-initialization
- ICQAMFX2 - Application manager function post-termination
- ICQAMPX1 - Application manager panel pre-display
- ICQAMPX2 - Application manager panel post-display
- IDYTSINI - TSOLIB initialization
- IDYTSTER - TSOLIB termination
- IKJADINI - ALTLIB initialization
- IKJADTER - ALTLIB termination
- IKJCNX50 - CONSOLE 80% message capacity
- IKJCNX60 - CONSOLE 100% message capacity
- IKJCNXAC - CONSOLE activation
- IKJCNXCD - CONSPROF pre-display
- IKJCNXCI - CONSPROF initialization
- IKJCNXCT - CONSPROF termination
- IKJCNXDE - CONSOLE deactivation
- IKJCNXPP - CONSOLE pre-parse
- IKJCT43I - EXEC initialization
- IKJCT43T - EXEC termination
- IKJCT44B - Add installation-written CLIST built-in functions
- IKJCT44S - Add installation-written CLIST statements
- IKJEESX0 - SEND initialization
- IKJEESX1 IEEVSNX1 - SEND pre-display
- IKJEESX2 IEEVSNX2 - SEND pre-save
- IKJEESX3 IEEVSNX3 - SEND failure
- IKJEESX4 IEEVSNX4 - SEND termination
- IKJEESX5 - LISTBC initialization
- IKJEESX6 - LISTBC pre-display
- IKJEESX7 - LISTBC pre-list
- IKJEESX8 - LISTBC pre-read
- IKJEESX9 - LISTBC pre-allocate
- IKJEESXA - LISTBC failure
- IKJEESXB - LISTBC termination
- IKJEFD21 - FREE initialization
- IKJEFD22 - FREE termination
- IKJEFD47 - ALLOCATE command initialization
- IKJEFD49 - ALLOCATE command termination
- IKJEFF10 - SUBMIT command
- IKJEFF53 - OUTPUT, STATUS and CANCEL commands
- IKJEFLD - Logon pre-prompt
- IKJEFLD1 - Logon authorized pre-prompt
- IKJEFLD2 - Logoff
- IKJEFLD3 - Logon post-prompt
- IKJEFLN1 - Logon pre-display
- IKJEFLN2 - Logon post-display
- IKJEFY11 - OUTDES initialization
- IKJEFY12 - OUTDES termination
- IKJEFY60 - -PRINTDS initialization
- IKJEFY64 - PRINTDS termination
- IKJEGASI - TESTAUTH subcommand initialization
- IKJEGAST - TESTAUTH subcommand termination
- IKJEGAUI - TESTAUTH initialization
- IKJEGAUT - TESTAUTH termination
- IKJEGCIE - TEST subcommand initialization
- IKJEGCTE - TEST subcommand termination
- IKJEGMIE - TEST initialization
- IKJEGMTE - TEST termination
- IKJPRMX1 - PARMLIB initialization
- IKJPRMX2 - PARMLIB termination
- INMCZ21R - TRANSMIT/RECEIVE NAMES data set pre-allocation
- INMRZ01 INMRZ01R - RECEIVE initialization
- INMRZ02 INMRZ02R - RECEIVE termination
- INMRZ04 INMRZ04R - RECEIVE notification
- INMRZ05R - RECEIVE acknowledgment notification
- INMRZ06R - RECEIVE pre-acknowledgment notification
- INMRZ11 INMRZ11R - RECEIVE data set preprocessing
- INMRZ12 INMRZ12R - RECEIVE data set postprocessing
- INMRZ13 INMRZ13R - RECEIVE data set decryption
- INMRZ15R - RECEIVE post-prompt
- INMRZ21R - RECEIVE log data set pre-allocation
- INMXZ01 INMXZ01R - TRANSMIT startup
- INMXZ02 INMXZ02R - TRANSMIT termination
- INMXZ03 INMXZ03R - TRANSMIT encryption
- INMXZ21R - TRANSMIT log data set pre-allocation
- IRXINITX - REXX pre-environment initialization
- IRXITTS IRXITMV - REXX post-environment initialization
- IRXTERMX - REXX environment termination
SMS exits
- CBRHADUX - Object access method (OAM) auto-delete
- CBRUXCUA - Change use attribute installation exit
- CBRUXEJC - Cartridge eject installation exit
- CBRUXENT - Cartridge entry installation exit
- IDAEOVXT - VSAM EOV installation exit
- IEFXVNSL - Automatic volume recognition (AVR) nonstandard label processing
- IFG0193G - ISO/ANSI/FIPS Version 3 label exits for volume access, file access, label validation, and label validation suppression
- IFG01991 - Open, close, end of volume abnormal conditions
- IFG0EX0A - Format-1 DSCB not found during OPEN or EOV
- IFG0EX0B - Take control during OPEN for a DCB
- IGBDCSX1 IGBDCSX2 - DASD precalculation and postcalculation services
- IGDACSDC - Automatic class selection (ACS) data class exit
- IGDACSMC - Automatic class selection (ACS) management class exit
- IGDACSSC - Automatic class selection (ACS) storage class exit
- IGG026DU - Catalog pre-initialization
- IGG029DM - Process after DADSM SCRATCH failure
- IGG029DU - DADSM SCRATCH pre-initialization
- IGG030DU - DADSM RENAME pre-initialization
- IGGDARU2 - DADSM RENAME preprocessing
- IGGDARU3 - DADSM RENAME postprocessing
- IGGDASU2 - DADSM SCRATCH preprocessing
- IGGDASU3 - DADSM SCRATCH postprocessing
- IGGPRE00 IGGPOST0 - DADSM preprocessing and postprocessing for allocate, extend, scratch, partial release and rename functions
- IGXMSGEX - Customize messages
- NSLETRLI - Nonstandard label processing for input trailers
- NSLETRLO NSLCTRLO - Nonstandard label processing for output trailers
- NSLOHDRI NSLEHDRI - Nonstandard label processing for input headers
- NSLOHDRO NSLEHDRO - Nonstandard label processing for output headers
- NSLREPOS - Volume verification using the dynamic device reconfiguration (DDR) option for nonstandard label processing
- NSLRHDRI - Nonstandard label processing for restarting after a checkpoint
- OMODVOL1 EMODVOL1 - Volume label editor for open and EOV
SMF exits
- USER1(name) - Exit routine receives control after each record is read by SMF dump program
- USER2(name) - Exit routine receives control only when the dump program selects a record to be written
- USER3(name) - Exit routine receives control after the output data set is closed by SMF dump program
- IEFACTRT - SMF Job and Job Step Termination Exit
- IEFU29 - SMF Dump Exit
- IEFU83 - SMF Record Exit
- IEFU84 - SMF Record Exit
- IEFU85 - SMF Record Exit
- JES2 EXIT 21 - SMF record
//SMFEXTR EXEC PGM=IFASMFDP
//STEPLIB DD DISP=SHR,DSN=RA2002.V3R7M0.LINKLIB
//OUTDD DD DISP=SHR,DSN=XRZP001.IRRADU00.OUTDDNEW,
// DCB=(RECFM=VB,LRECL=12288)
//ADUPRINT DD SYSOUT=*
//SMFDATA1 DD DSN=XRZP001.SMF.ALS$1003,DISP=OLD
//SMFOUT DD DSN=&&SMFFILE,
// DISP=(,PASS),
// DCB=(RECFM=VBS,LRECL=32760,BLKSIZE=6240),
// UNIT=SYSDA,SPACE=(TRK,(1,1))
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
INDD(SMFDATA1,OPTIONS(DUMP))
ABEND(NORETRY)
OUTDD(SMFOUT,TYPE(80))
USER2(SMF$XT30)
USER3(SMF$XT31)
/*
//FLTPRINT DD SYSOUT=*
//FLTINPUT DD *
+INCLUDE COND=((0006,1,HX,EQ,50),AND,
((0001(0004,H38,H40,I1,0),1,HX,EQ,04),AND,
(0001(0004,H38,H40,I1,2),01,HX,EQ,80)),AND,
((0001(0004,H38,H40,I1,0),1,HX,EQ,01),AND,
(0001(0004,H38,H40,I1,2),00,CG,EQ,RA**)))
//
SDSF exit
- ISFUSER
The installation exit points within SDSF link to the ISFUSER module at entry point ISFUSER. SDSF provides the following exit points for installation routines to customize authorization: |
- Initialization - Who can use SDSF
- Command Authority - Which commands users can issue
- SYSOUT Display Authority - For which jobs users can display output
- SDSF termination - Termination processing
- Pre-SAF - How the SAF authorization decision is to be made-
- Post-SAF - Accept or ignore result of SAF authorization
- SAF indeterminate - Action for SAF indeterminate responses
- Table build - What is displayed on tabular panels
RACF exits
- ICHCCX00 Command exit
- ICHCNX00 Command exit
- ICHDEX01 RACF password authentication
- ICHFRX01 RACROUTE request=FASTAUTH pre-processing
- ICHFRX02 RACROUTE request=FASTAUTH post-processing
- ICHPWX01 New password exit
- ICHRCX01 RACROUTE request=AUTH pre-processing
- ICHRCX02 RACROUTE request=AUTH post-processing
- ICHRDX01 RACROUTE request=DEFINE pre-processing
- ICHRDX02 RACROUTE request=DEFINE post-processing
- ICHRIX01 RACROUTE request=VERIFY pre-processing
- ICHRIX02 RACROUTE request=VERIFY post-processing
- ICHRLX01 RACROUTE request=LIST pre-/post-processings
- ICHRLX02 RACROUTE request=LIST selection
- ICHRSMFE RACF report writer
- IRRACX01 ACEE compre-ssion/expansion
- IRREVX01 Common command exit
- ICHRFX03 RACROUTE request=FASTAUTH pre-processing
- ICHRFX04 RACROUTE request=FASTAUTH post-processing
- IRRSXT00 SAF callable services router
JES2 exits
- Exit 0 - Pre-initialization
- Exit 1 - Print/Punch Separators
- Exit 2 - JOB Statement Scan
- Exit 3 - JOB Statement Accounting Field Scan
- Exit 4 - JCL and JES2 Control Statement Scan
- Exit 5 - JES2 Command Preprocessor
- Exit 6 - Converter/Interpreter Text Scan
- Exit 7 - JCT Read/Write (JES2)
- Exit 8 - Control Block Read/Write (USER)
- Exit 9 - Job Output Overflow
- Exit 10 - $WTO Screen
- Exit 11 - Spool Partitioning Allocation ($TRACK)
- Exit 12 - Spool Partitioning Allocation ($STRAK)
- Exit 13 - TSO/E Interactive Data Transmission Facility Screening and Notification
- Exit 14 - Job Queue Work Select -- $QGET
- Exit 15 - Output Data Set/Copy Select
- Exit 16 - Notify
- Exit 17 - BSC RJE SIGNON/SIGNOFF
- Exit 18 - SNA RJE LOGON/LOGOFF
- Exit 19 - Initialization Statement
- Exit 20 - End of Input
- Exit 21 - SMF Record
- Exit 22 - Cancel/Status
- Exit 23 - FSS Job Separator Page (JSPA) Processing
- Exit 24 - Post-initialization
- Exit 25 - JCT Read (FSS)
- Exit 26 - Termination/Resource Release
- Exit 27 - PCE Attach/Detach
- Exit 28 - Subsystem Interface (SSI) Job Termination
- Exit 29 - Subsystem Interface (SSI) End-of-Memory
- Exit 30 - Subsystem Interface (SSI) Data Set OPEN and RESTART
- Exit 31 - Subsystem Interface (SSI) Allocation
- Exit 32 - Subsystem Interface (SSI) Job Selection
- Exit 33 - Subsystem Interface (SSI) Data Set CLOSE
- Exit 34 - Subsystem Interface (SSI) Data Set Unallocation
- Exit 35 - Subsystem Interface (SSI) End-of-Task
- Exit 36 - Pre-security Authorization Call
- Exit 37 - Post-security Authorization Call
- Exit 38 - TSO/E Receive Data Set Disposition
- Exit 39 - NJE SYSOUT Reception Data Set Disposition
- Exit 40 - Modifying SYSOUT Characteristics
- Exit 41 - Modifying Output Grouping Key Selection
- Exit 42 - Modifying a Notify User Message
- Exit 43 - Transaction Program Select/Terminate/Change
- Exit 44 - JES2 Converter Exit (Main Task)
- Exit 45 - Pre-SJF Exit Request
- Exit 46 - Transmitting an NJE Data Area
- Exit 47 - Receiving an NJE Data Area
CICS exits
Exit name | Module or domain | Where or when invoked | Page |
XAKUSER | Activity keypoint program | Immediately before the ‘end of keypoint’ record is written. | Exit XAKUSER |
XALCAID | Terminal allocation program | Whenever an AID with data is canceled. | Exit XALCAID |
XALTENF | Terminal allocation program | When an ATI request from transient data or interval control requires a terminal that is unknown in this system. | Exit XALTENF |
XBMIN | Basic Mapping Support | When an input mapping operation completes successfully. | Exit XBMIN |
XBMOUT | Basic Mapping Support | When a page of output has been built successfully. | Exit XBMOUT |
XDLIPOST | DL/I interface program | On exit from the DL/I interface program. | Exit XDLIPOST |
XDLIPRE | DL/I interface program | On entry to the DL/I interface program. | Exit XDLIPRE |
XDSAWT | Dispatcher domain | After an operating system wait. | Exit XDSAWT |
XDSBWT | Dispatcher domain | Before an operating system wait. | Exit XDSBWT |
XDTAD | Data tables management | When a write request is issued to a data table. | Exit XDTAD |
XDTLC | Data tables management | At the completion of loading of a data table. | Exit XDTLC |
XDTRD | Data tables management | During the loading of a data table, whenever a record is retrieved from the source data set. | Exit XDTRD |
XDUCLSE | Dump domain | After the domain closes a transaction dump data set. | Exit XDUCLSE |
XDUOUT | Dump domain | Before the domain writes a record to the transaction dump data set. | Exit XDUOUT |
XDUREQ | Dump domain | Before the domain takes a system or transaction dump. | Exit XDUREQ |
XDUREQC | Dump domain | After a system or transaction dump has been taken (or failed or been suppressed). | Exit XDUREQC |
XEIIN | EXEC interface program | Before the execution of any EXEC CICS API or SPI command. | Exit XEIIN |
XEIOUT | EXEC interface program | After the execution of any EXEC CICS API or SPI command. | Exit XEIOUT |
XEISPIN | EXEC interface program | Before the execution of any EXEC CICS SPI command. | Exit XEISPIN |
XEISPOUT | EXEC interface program | After the execution of any EXEC CICS SPI command. | Exit XEISPOUT |
XFAINTU | 3270 bridge facility management program | When a bridge facility is created or deleted. | Exit XFAINTU |
XFCAREQ | File control EXEC interface program | Before CICS® processes a file control SPI request. | File control EXEC interface SPI exits XFCAREQ and XFCAREQC |
XFCAREQC | File control EXEC interface program | After a file control SPI request has completed. | File control EXEC interface SPI exits XFCAREQ and XFCAREQC |
XFCBFAIL | File control recovery control program | When an error occurs during the backout of a UOW. | Exit XFCBFAIL, file control backout failure exit |
XFCBOUT | File control recovery control program | When CICS is about to back out a file update. | Exit XFCBOUT, file control backout exit |
XFCBOVER | File control recovery control program | When CICS is about to skip backout of a UOW because a batch program has overridden RLS retained lock protection and opened a data set for batch processing. | Exit XFCBOVER, file control backout override exit |
XFCFRIN | File control domain | Before the execution of a file control request. | XFCFRIN |
XFCFROUT | File control domain | After the execution of a file control request. | XFCFROUT |
XFCLDEL | File control recovery control program | When backing out writes to a VSAM ESDS or a BDAM data set. | Exit XFCLDEL, file control logical delete exit |
XFCNREC | File control open/close program | When a mismatch is detected between the backout recovery setting for a file and its associated data set during file open processing. | Exit XFCNREC |
XFCQUIS | File control quiesce send program | On completion, successful or failed, of a SET DSNAME QUIESCESTATE command. | File control quiesce send exit XFCQUIS |
XFCREQ | File control EXEC interface program | Before CICS processes a file control API request. | Exit XFCREQ |
XFCREQC | File control EXEC interface program | After a file control API request has completed. | Exit XFCREQC |
XFCSREQ | File control file state program | Before a file OPEN, CLOSE, ENABLE, or DISABLE command is attempted. | File control file state program exits XFCSREQ and XFCSREQC |
XFCSREQC | File control file state program | After a file OPEN, CLOSE, CANCEL CLOSE, ENABLE, or DISABLE command has been completed. | File control file state program exits XFCSREQ and XFCSREQC |
XFCVSDS | File control quiesce receive program | After RLS has informed CICS that processing is required as a result of a data set-related action occurring in the sysplex. | File control quiesce receive exit, XFCVSDS |
XGMTEXT | "Good morning" message program | Before the "good morning" message is sent. | "Good morning" message program exit XGMTEXT |
XICEREQ | Interval control EXEC interface program | Before CICS processes an interval control API request. | Exit XICEREQ |
XICEREQC | Interval control EXEC interface program | After an interval control API request has completed. | Exit XICEREQC |
XICERES | Interval control EXEC interface program | Before CICS processes a non-terminal-related EXEC CICS START request that has been dynamically routed to this region, where the routing region supports the "resource unavailable" (RESUNAVAIL) condition. | Exit XICERES |
XICEXP | Interval control program | After expiry of an interval control time interval. | Exit XICEXP |
XICREQ | Interval control program | At the start of the interval control program, before request analysis. | Exit XICREQ |
XICTENF | Interval control program | When an EXEC CICS START command requires a terminal that is unknown in this system. | Exit XICTENF |
XISCONA | Intersystem communication program | When a function shipping or DPL request is about to be queued because no sessions to the remote region are immediately available. | Intersystem communication program exits XISCONA and XISLCLQ |
XISLCLQ | Intersystem communication program | After an attempt to allocate a session for a function shipped START NOCHECK request fails because the remote system is not in service, a connection to the remote system cannot be established, or no sessions are immediately available and your XISCONA exit program has specified that the request is not to be queued in the issuing region. | The XISLCLQ exit |
XLDELETE | Loader domain | After an instance of a program is released by CICS and just before the program is freed from storage. | Exit XLDELETE |
XLDLOAD | Loader domain | After an instance of a program is brought into storage, and before the program is made available for use. | Exit XLDLOAD |
XLGSTRM | Log manager domain | After the CICS log manager detects that a log stream does not exist, and before calling the MVS™ system logger to define the log stream. | Log manager domain exit XLGSTRM |
XMEOUT | Message domain | Before a message is sent from the message domain to its destination. | Exit XMEOUT |
XMNOUT | Monitoring domain | Before a record is either written to SMF or buffered before a write to SMF. | Exit XMNOUT |
XNQEREQ | Enqueue EXEC interface program | Before CICS processes an enqueue API request. | Exit XNQEREQ |
XNQEREQC | Enqueue EXEC interface program | After an enqueue API request has completed. | Exit XNQEREQC |
XPCABND | Program control program | After a transaction abend and before a dump call is made. | Exit XPCABND |
XPCERES | Program control program | Before CICS processes a program link or Link3270 bridge request that has been dynamically routed to this region, where the routing region supports the "resource unavailable" (RESUNAVAIL) condition. | Exit XPCERES |
XPCFTCH | Program control program | Before an application program is given control. | Exit XPCFTCH |
XPCHAIR | Program control program | Before a HANDLE ABEND routine is given control. | Exit XPCHAIR |
XPCREQ | Program control program | Before a LINK request is processed. | Exit XPCREQ |
XPCREQC | Program control program | After a LINK request has been completed. | Exit XPCREQC |
XPCTA | Program control program | After an abend occurs, and before the environment is modified. | Exit XPCTA |
XRCINIT | User log record recovery program | During warm and emergency restart, if user recovery log records are detected in the CICS system log. | Exit XRCINIT |
XRCINPT | User log record recovery program | During warm and emergency restart, for each user recovery log record found in the CICS system log. | Exit XRCINPT |
XRMIIN | Resource manager interface program | Before execution of an EXEC DLI, EXEC SQL, or RMI command. | Exit XRMIIN |
XRMIOUT | Resource manager interface program | After execution of an EXEC DLI, EXEC SQL, or RMI command. | Exit XRMIIN |
XRSINDI | Resource management modules | Immediately after a successful install or discard of a resource. | Resource management install and discard exit XRSINDI |
XSNEX | Security manager domain | Restore old CICS signon and signoff behavior (pre-CICS TS 2.1) | Exit XSNEX |
XSNOFF | Security manager domain | After a terminal user signs off. | Exit XSNOFF |
XSNON | Security manager domain | After a terminal user signs on. | Exit XSNON |
XSRAB | System recovery program | When the system recovery program finds a match for an MVS abend code in the SRT. | Exit XSRAB |
XSTERM | System termination program | During a normal system shutdown, immediately before TD buffers are cleared. | Exit XSTERM |
XSTOUT | Statistics domain | Before a statistics record is written to SMF. | Exit XSTOUT |
XSZARQ | Front End Programming Interface | After a FEPI request has completed. | Front End Programming Interface exits XSZARQ and XSZBRQ |
XSZBRQ | Front End Programming Interface | Before a FEPI request is actioned. | Front End Programming Interface exits XSZARQ and XSZBRQ |
XTCATT | Terminal control program | Before task attach. | Exit XTCATT |
XTCIN | Terminal control program | After an input event. | Exit XTCIN |
XTCOUT | Terminal control program | Before an output event. | Exit XTCOUT |
XTDEREQ | Transient data EXEC interface program | Before CICS processes a transient data API request. | Exit XTDEREQ |
XTDEREQC | Transient data EXEC interface program | After a transient data API request has completed. | Exit XTDEREQC |
XTDIN | Transient data program | After receiving data from QSAM (extrapartition) or VSAM (intrapartition). | Exit XTDIN |
XTDOUT | Transient data program | Before passing data to a QSAM (extrapartition) or VSAM (intrapartition) user-defined transient data queue. | Exit XTDOUT |
XTDREQ | Transient data program | Before request analysis. | Exit XTDREQ |
XTSEREQ | Temporary storage EXEC interface program | Before CICS processes a temporary storage API request. | Exit XTSEREQ |
XTSEREQC | Temporary storage EXEC interface program | After a temporary storage API request has completed. | Exit XTSEREQC |
XTSPTIN | Temporary storage domain | Before invocation of a TSPT function. | Exit XTSPTIN |
XTSPTOUT | Temporary storage domain | After invocation of a TSPT function. | Exit XTSPTOUT |
XTSQRIN | Temporary storage domain | Before invocation of a TSQR function. | Exit XTSQRIN |
XTSQROUT | Temporary storage domain | After invocation of a TSQR function. | Exit XTSQROUT |
XWBOPEN | Web domain | During processing of an EXEC CICS WEB OPEN command. | HTTP client open and send exits, XWBOPEN and XWBSNDO |
XWBSNDO | Web domain | During processing of an EXEC CICS WEB SEND command. | HTTP client open and send exits, XWBOPEN and XWBSNDO |
XXDFA | DBCTL interface control program | In the active CICS when CICS-DBCTL connection fails. | DBCTL interface control program exit XXDFA |
XXDFB | DBCTL tracking program | In the alternate CICS when DBCTL fails. | Exit XXDFB |
XXDTO | DBCTL tracking program | In the alternate CICS when active DBCTL fails. | Exit XXDTO |
XXMATT | Transaction manager domain | When a user transaction is attached. | Exit XXMATT |
XXRSTAT | XRF request processing program | After a VTAM® failure or a predatory takeover. | Exit XXRSTAT |
XZCATT | VTAM terminal management program | Before task attach. | Exit XZCATT |
XZCIN | VTAM working set module | After an input event. | Exit XZCIN |
XZCOUT | VTAM working set module | Before an output event. | Exit XZCOUT |
XZCOUT1 | VTAM working set module | Before a message is broken into RUs. | Exit XZCOUT1 |
XZIQUE | VTAM working set module | When an allocate request for a session is about to be queued. When an allocate request succeeds following previous suppression of queuing. | XZIQUE exit for managing intersystem queues |
訂閱:
文章 (Atom)