Cross coupling facility Commands SYSPLEX XCF DISPLAY COMMANDS |
||||||
---------------------------- | ||||||
D XCF | - | DISPLAYS STATUS OF XCF DEVICES | ||||
D XCF,ARMSTATUS | - | DISPLAYS ACTIVE REGISTERED ELEMENTS | ||||
D XCF,CF | - | DISPLAYS COUPLING NAMES & INFO | ||||
D XCF,CF,CFNM=#### | - | DISPLAYS CFRM INFO BY NAME | ||||
D XCF,CLASSDEF | - | DISPLAYS TRANSPORT CLASSES DEFINED | ||||
D XCF,COUPLE | - | DISPLAYS CURRENT XCF COUPLE INFO | ||||
D XCF,GROUP | - | DISPLAYS SIGNALLING RESOURCE INFO | ||||
D XCF,LOCALMSG | - | DISPLAYS SIGNALLING RESOURCE INFO | ||||
D XCF,PATHIN | - | XCF SIGNALLING PATHIN STATUS | ||||
D XCF,PATHIN,DEVICE=ALL | - | XCF SIGNALLING PATHIN STATUS | ||||
D XCF,PATHIN,STRN=ALL | - | ????? ( UPDATE THIS ) ???????? | ||||
D XCF,PATHOUT | - | XCF SIGNALLING PATHOUT STATUS | ||||
D XCF,PATHOUT,DEVICE=ALL | - | XCF SIGNALLING PATHOUT STATUS | ||||
D XCF,POLICY | - | DISPLAYS ALL POLICY INFOMATION | ||||
D XCF,POLICY,TYPE | - | DISPLAYS SPECIFIC POLICY INFO | ||||
D XCF,SYSPLEX ALL | - | DISPLAYS ALL SYSTEMS IN SYSPLEX | ||||
D XCF,STR=STRM=ALL | - | DISPLAYS ALL STRUCTURES | ||||
D XCF,STRUCTURE | - | DISPLAYS LIST OF CFRM POLICIES | ||||
SYSPLEX XCF SET COMMANDS | ||||||
---------------------------- | ||||||
SETXCF | - | TO CONTROL XCF (DEVICES) | ||||
SETXCF,COUPLE,ACOUPLE=(####) | - | SPECIFY ALTERNATE XCF COUPLE DATASET | ||||
SETXCF,COUPLE,CLASSLEN= | - | SPECIFY LENGTH OF TRANSPORT CLASSES | ||||
SETXCF,COUPLE,CLEANUP= | - | SPECIFY THE LENGTH OF CLEANUP * | ||||
SETXCF,COUPLE,INTERVAL= | - | SPECIFY THE LENGTH OF INTERVAL * | ||||
SETXCF,COUPLE,MAXMSG= | - | SPECIFY DEFAULT MAX MESSAGE BUFFERS | ||||
SETXCF,COUPLE,OPNOTIFY= | - | SPECIFY THE LENGTH OF XCF NOTIFY * | ||||
SETXCF,COUPLE,PSWITCH | - | SWITCH THE PRIMARY COUPLE DATASET | ||||
SETXCF,COUPLE,RETRY= | - | SPECIFY DEFAULT RETRY LIMIT * | ||||
SETXCF,COUPLE,TYPE= | - | SPECIFY TYPE OF DATE STORED * | ||||
SETXCF,FORCE,CON | - | REMOVES THE ALLLOCATION | ||||
SETXCF,MODIFY,----- | - | CHANGES CURRENT XCF PARAMETERS | ||||
SETXCF,PRSMPOLICY,------ | - | ACTIVATE/DEACTIVATE PR/SM POLICY | ||||
SETXCF,START,ALTER,----- | - | SPECIFY STRUCTURE TO ALTERED | ||||
SETXCF,START,CLASSDEF,----- | - | SPECIFY DEFINITION OF TRANSPORT CLASS | ||||
SETXCF,START,REBUILD,STRNAME, | - | SPECIFY STRUCTURE TO BE REBUILT | ||||
SETXCF,START,PATHIN,----- | - | START SIGNALING PATHS AND DEFINE * | ||||
SETXCF,START,PATHOUT,----- | - | START SIGNALING PATHS AND DEFINE * | ||||
SETXCF,START,POLICY,TYPE= | - | SPECIFY NAME USING COUPLE DATASET | ||||
SETXCF,START,POLICY,POLNAME= | - | TO ACTIVATE POLICY BY NAME | ||||
SETXCF,STOP,ALTER,----- | - | SPECIFY STRUCTURE ALTERNING TO STOP | ||||
SETXCF,STOP,CLASSDEF,----- | - | DELETE DEFINITION OF TRANSPORT CLASS | ||||
SETXCF,STOP,REBUILD,STRNAME, | - | SPECIFY STRUCTURE REBUILT TO STOP | ||||
SETXCF,STOP,PATHIN,----- | - | STOP SIGNALING PATHS AND DEFINE * | ||||
SETXCF,STOP,PATHOUT,----- | - | STOP SIGNALING PATHS AND DEFINE * | ||||
SETXCF,STOP,PATHOUT,----- | - | STOP SIGNALING PATHS AND DEFINE * | ||||
Thursday, January 23, 2014
XCF commands
Tuesday, January 21, 2014
Stopping JES2
To stop JES2
$PJES2
If $Pjes2 not working then we can use ABEND or TERM commands as follows.
Note :
If JES2 is processing any jobs or any devices are active then we cannot remove JES without ABEND or TERM command.In some cases active RJE and NJE lines also prevents JES2 to stop and in such scenario JES2 processing will stop whereas JES2 display commands will work.JES2 will be dormant.
$pjes2,abend
Jes2 terminates immediately killing all system activity,except in one scenario where any checkpoint resides on coupling facility processing a write request.In such scenario $HASP552 and delays executing ABEND command until the checkpoint completes.
If ABEND not working we have to use FORCE.
$PJES2,ABEND,FORCE
Command will pull Recovery Termination Manager(RTM) to immedietely terminate the JES2 address space.
$PJES2,QUICK
Jes2 attempts to withdraw completely,regardless of any cross-system activity.
$PJES2,TERM
Jes2 terminates but does not terminate active devices and programs.Jes2 hot start will not be possible,need to clear address space before bringing down MVS. This command requires system authority.
$PJES2
If $Pjes2 not working then we can use ABEND or TERM commands as follows.
Note :
If JES2 is processing any jobs or any devices are active then we cannot remove JES without ABEND or TERM command.In some cases active RJE and NJE lines also prevents JES2 to stop and in such scenario JES2 processing will stop whereas JES2 display commands will work.JES2 will be dormant.
$pjes2,abend
Jes2 terminates immediately killing all system activity,except in one scenario where any checkpoint resides on coupling facility processing a write request.In such scenario $HASP552 and delays executing ABEND command until the checkpoint completes.
If ABEND not working we have to use FORCE.
$PJES2,ABEND,FORCE
Command will pull Recovery Termination Manager(RTM) to immedietely terminate the JES2 address space.
$PJES2,QUICK
Jes2 attempts to withdraw completely,regardless of any cross-system activity.
$PJES2,TERM
Jes2 terminates but does not terminate active devices and programs.Jes2 hot start will not be possible,need to clear address space before bringing down MVS. This command requires system authority.
Saturday, January 18, 2014
Z EOD
The HALT EOD command causes the system to take the following steps:
- Store the internal I/O device error counts in the logrec data set.
- Empty the SMF buffers onto the active SMF data set in SYS1.MANx.
- Switch to another SMF data set in SYS1.MANx, allowing the previously active SMF data set to be dumped according to your installation's procedures.
- Close the system log and put it on the print queue.
When these actions are completed, the system sends you the message:
IEE334I HALT EOD SUCCESSFUL.
OMVS
z/OS provides access to a Unix based environment via Unix System Services (USS). USS can run many Unix programs, shell scripts, and services. USS is also able to take advantage of many core z/OS features, and it can be accessed directly from TSO via two methods: ISHELL (ish) or OMVS. ISHELL provides an interface that those comfortable with TSO commands will find intuitive. OMVS is oriented towards those who are more comfortable with standard Unix commands.
PARMLIB
BPXPRMxx
Starting OMVS
S OMVS,OMVS=xx
xx denotes parmlib member for BPXPRMxx
Shutdown OMVS
1831344 -F OMVS,SHUTDOWN
1831345 SYSA R= OMVS BPXI055I OMVS SHUTDOWN REQUEST ACCEPTED
Displaying status of OMVS
1831240 -D OMVS,S
1831241 SYSA R= BPXO042I 18.31.24 DISPLAY OMVS 186
1831241 SYSA R= OMVS 000E ACTIVE OMVS=(00,FS,F1)
1832267 -D OMVS,S
1832268 SYSA R= BPXO042I 18.32.26 DISPLAY OMVS 236 1832268 SYSA R= OMVS 000E SHUTTING DOWN 3 OMVS=(00,FS,F1)
1832487 -D OMVS,S
1832487 SYSA R= BPXO042I 18.32.48 DISPLAY OMVS 269
1832487 SYSA R= OMVS 000E SHUTDOWN
Restarting OMVS
F OMVS,RESTART
D OMVS,A=ALL
Display all active process in OMVS
15.39.35 d omvs,a=all
15.39.35 SYSA BPX12345 15.39.35 DISPLAY OMVS 519 C
OMVS 000E ACTIVE OMVS=(00,S3)
USER JOBNAME ASID PID PPID STATE START CT_SECS
SYSPROC RESOLVER 000F 2 1 1R---B-- 01.43.17 12.7
LATCHWAITPID= 0 CMD=asdfgf
SYSPROC RESOLVER 000F 3 1 1R---B-- 01.43.17 12.7
LATCHWAITPID= 0 CMD=EZXXXXX
D OMVS,PID=nnn
Displays the status of individual Process and thread with process ID
nnn=process ID
15.49.45 d omvs,pid=2 15.49.45 SYSA BPX12345 15.49.45 DISPLAY OMVS 644 OMVS 000E ACTIVE OMVS=(00,S3) USER JOBNAME ASID PID PPID STATE START CT_SECS SYSPROC RESOLVER 000F 2 1 1R---B-- 01.43.17 12.7 LATCHWAITPID= 0 CMD=asdfgf THREAD_ID TCB@ PRI_JOB USERNAME ACC_TIME SC STATE 1191E90000000000 008FF260 .057 NOP Y
D OMVS,W
Dispplays mount latch and cross system message
16.03.23 d omvs,w
16.03.23 SYSA BPXO063I 16.03.23 DISPLAY OMVS 756
OMVS 000E ACTIVE OMVS=(00,S3)
MOUNT LATCH ACTIVITY: NONE
FILE SYSTEM LATCH ACTIVITY: NONE
FILE LATCH ACTIVITY: NONE
OTHER WAITING THREADS: NONE
D OMVS,F
Displays file system latch and mount time and date information
16.04.18 D OMVS,F
16.04.18 SYSA BPXO045I 16.04.18 DISPLAY OMVS 763
OMVS 000E ACTIVE OMVS=(00,S3)
TYPENAME DEVICE ----------STATUS----------- MODE MOUNTED LATCHES
ZFS 8 ACTIVE RDWR 11/03/2013 L=19
NAME=LSE.CMF.S0S3.CASRGRY 01.43.16 Q=0
PATH=/usr/MAINVIEW
MOUNT PARM=FSFULL(75,5)
D OMVS,MF
Information about mount file system failures(displays last 10 failures)
16.08.07 d omvs,mf
16.08.07 SYSA BPXO058I 16.08.07 DISPLAY OMVS 771
OMVS 000E ACTIVE OMVS=(00,S3)
NO MOUNT OR MOVE FAILURES TO DISPLAY
D OMVS,MF=ALL
Displays up to 50 failures
D OMVS,MF=PURGE
deleted failure information log
D OMVS,SO
Displays OMVS sockets
PARMLIB
BPXPRMxx
Starting OMVS
S OMVS,OMVS=xx
xx denotes parmlib member for BPXPRMxx
Shutdown OMVS
1831344 -F OMVS,SHUTDOWN
1831345 SYSA R= OMVS BPXI055I OMVS SHUTDOWN REQUEST ACCEPTED
Displaying status of OMVS
1831240 -D OMVS,S
1831241 SYSA R= BPXO042I 18.31.24 DISPLAY OMVS 186
1831241 SYSA R= OMVS 000E ACTIVE OMVS=(00,FS,F1)
1832267 -D OMVS,S
1832268 SYSA R= BPXO042I 18.32.26 DISPLAY OMVS 236 1832268 SYSA R= OMVS 000E SHUTTING DOWN 3 OMVS=(00,FS,F1)
1832487 -D OMVS,S
1832487 SYSA R= BPXO042I 18.32.48 DISPLAY OMVS 269
1832487 SYSA R= OMVS 000E SHUTDOWN
Restarting OMVS
F OMVS,RESTART
D OMVS,A=ALL
Display all active process in OMVS
15.39.35 d omvs,a=all
15.39.35 SYSA BPX12345 15.39.35 DISPLAY OMVS 519 C
OMVS 000E ACTIVE OMVS=(00,S3)
USER JOBNAME ASID PID PPID STATE START CT_SECS
SYSPROC RESOLVER 000F 2 1 1R---B-- 01.43.17 12.7
LATCHWAITPID= 0 CMD=asdfgf
SYSPROC RESOLVER 000F 3 1 1R---B-- 01.43.17 12.7
LATCHWAITPID= 0 CMD=EZXXXXX
D OMVS,PID=nnn
Displays the status of individual Process and thread with process ID
nnn=process ID
15.49.45 d omvs,pid=2 15.49.45 SYSA BPX12345 15.49.45 DISPLAY OMVS 644 OMVS 000E ACTIVE OMVS=(00,S3) USER JOBNAME ASID PID PPID STATE START CT_SECS SYSPROC RESOLVER 000F 2 1 1R---B-- 01.43.17 12.7 LATCHWAITPID= 0 CMD=asdfgf THREAD_ID TCB@ PRI_JOB USERNAME ACC_TIME SC STATE 1191E90000000000 008FF260 .057 NOP Y
D OMVS,W
Dispplays mount latch and cross system message
16.03.23 d omvs,w
16.03.23 SYSA BPXO063I 16.03.23 DISPLAY OMVS 756
OMVS 000E ACTIVE OMVS=(00,S3)
MOUNT LATCH ACTIVITY: NONE
FILE SYSTEM LATCH ACTIVITY: NONE
FILE LATCH ACTIVITY: NONE
OTHER WAITING THREADS: NONE
D OMVS,F
Displays file system latch and mount time and date information
16.04.18 D OMVS,F
16.04.18 SYSA BPXO045I 16.04.18 DISPLAY OMVS 763
OMVS 000E ACTIVE OMVS=(00,S3)
TYPENAME DEVICE ----------STATUS----------- MODE MOUNTED LATCHES
ZFS 8 ACTIVE RDWR 11/03/2013 L=19
NAME=LSE.CMF.S0S3.CASRGRY 01.43.16 Q=0
PATH=/usr/MAINVIEW
MOUNT PARM=FSFULL(75,5)
D OMVS,MF
Information about mount file system failures(displays last 10 failures)
16.08.07 d omvs,mf
16.08.07 SYSA BPXO058I 16.08.07 DISPLAY OMVS 771
OMVS 000E ACTIVE OMVS=(00,S3)
NO MOUNT OR MOVE FAILURES TO DISPLAY
D OMVS,MF=ALL
Displays up to 50 failures
D OMVS,MF=PURGE
deleted failure information log
D OMVS,SO
Displays OMVS sockets
Monday, January 13, 2014
JES3 commands
JES3 Commands | |
JES stands for Job Entry Subsystem | |
COMMANDS | DESCRIPTION |
*C RJP,L=ALL,I | Terminates all BSC lines immediately |
*C RJP,L-LILNEnn,I | Terminates BSC line immediately |
*C SNAJP,T=ALL,I | Terminates SNA remote immediately |
*C SNARJP,T=ALL,I | Terminates all SNA lines immediately |
*DUMP | Cancel JES immediately with a dump |
*F C=X MDEPTH=X | Change the mdepth of class X to X |
*F G,SYn,G,group,off | Drain specified initiators |
*F G,Syn,G,'GROUPNAME',15 | Start 15 initiators of a specified group |
*F G,A3,C,P,ON | Start all class P initiators on system A3 |
*F G,SYn,group,OFF | Halt specified group (init) |
*F G,SYn,GROUP,ON | Start a specified group (init) |
*F G,SYn,S MODE,NULL | Drain all initiators |
*F J=jobname,C | Cancel job without output |
*F J=jobname,CO | Cancel job with output |
*F J=jobname,H | Place a job on hold by jobname |
*F J=jobname,H | Stop (purge) jobname after processing completes |
*F J=jobname,P=nn | Set jobname to priority nn |
*F J=xxxx,H | Place job on hold |
*F J=xxxx,H | Stop (purge) job after processing completes |
*F J=xxxx,P=nn | Set job priority |
*F Q,H | Modify queue to hold jobs |
*F Q,P=n,R | Modify queue to release all priority n jobs |
*F Q,P=n,R | Inquire/list the top 10 job with priority of NN |
*F Q,P=nn,H | Modify queue to hold all priority n jobs |
*F S,VA=T-volser | Make volser available |
*F S,VU=T-volser | Place volser in MDS unavailable queue |
*F U,D=Rnnnn,ND=Rnnnn,N=ALL | Route all output from one remote to another |
*F U,J=xxxx,D=Rnnnn,ND=Rnnnn | Route output of job to a new destination |
*F U,J=xxxx,NP=nn | Set output for job to new priority |
*F U,J=xxxx,Q=HOLD,CL=C | Cancel held output for job xxxx in class C |
*F U,J=xxxx,Q=HOLD,NCL=c | Release job from held output to process class C |
*F U,J=xxxx,Q=HOLD,NQ,WTR,ND=device | Release job from held output to print device |
*f u q=hold,age=5d,n=100,c | Cancels first 100 , jobs which are 5 days old |
*I B | Inquire on backlog summary total by JES phases |
*I B,M | Inquire on backlog for jobs waiting conversion |
*I B,SYn | Inquire on backlog for jobs waiting execution on SYn |
*I B,T=Rnnnn | Inquire on backlog for jobs from remote |
*I C=P | Inquire on class P initiators |
*I D D,R=nnnndevice | Inquire on status of remote device |
*I D D='DEVNUM',N='64' | Inquire on device 800 plus the following 64 devices |
*I D,D=device | Inquire on status of local device |
*I D,L=ALL | Inquire on status of all BSC remote lines |
*I D,L=LNEnn | Inquire on status of BSC line nn |
*I D,T=ALL | Inquire on status of all SNA remote lines |
*I D,T=ALL,ONLINE | Inquire on all BSC and SNA remotes online |
*I D,T=Rnnnn | Inquire on status of remote |
*I G,SYn,C | Inquire on status of all classes eligible for SYn |
*I G,SYn,G | Inquire on status for all groups eligible for Syn |
*I J=job* | Display all jobnames beginning with job |
*I J=jobname | Display status of a job by jobname |
*I J=xxxx | Display status of a job |
*I J=Xxxxx,E | Display estimated number of lines created |
*I P=nn,N-ALL | Inquire/list all jobs with a priority of nn |
*I Q,C=c,N=ALL | Display all jobs in class C waiting execution |
*I Q,D=MAIN,N=ALL | Display all jobs in queue waiting execution |
*I Q,H,N=ALL | Inquire on queue for all jobs on hold |
*I Q,N=ALL | Display status of all jobs in the queue |
*I Q,S | Inquire on queue for spool space unused |
*I Q,SP=ALL | Inquire on queue for all spool volumes |
*I Q,SP=ALL,U | displays jobs using more spool |
*I Q,S=SETUP,N=ALL | Display all jobs in SETUP class group |
*I Q,T=Rxxxx,N=ALL | Display all jobs waiting in output queue at remote |
*I R | Inquire on all outstanding replies except MDS |
*I R,S | Inquire on outstanding MDS (setup) replies/mounts |
*I R,S,J=xxxx | Inquire on replies for setup messages for job xxxx |
*I R,SYn | Inquire on outstanding replies for Syn |
*I S | Inquire for a summary of scheduled jobs in MDS |
*I S A | Inquire on scheduled jobs in MDS allocate queue |
*I S A,J=xxxx | Inquire on reason job xxxx is in MDS allocate queue |
*I S,B | Inquire on scheduled jobs in MDS breakdown queue |
*I S DE='DATASET/DEVICE' | Inquire on what is holding a dataset or device |
*I S,E | Inquire on scheduled jobs in MDS error queue |
*I S,E,J=xxxx | Inquire on reason job is in MDS error queue |
*I S,R | Inquire on schedule jobs in MDS restart queue |
*I S,U | Inquire on schedule jobs in MDS unavailable queue |
*I S,V | Inquire on scheduled jobs in MDS verify queue |
*I S,V=ALL | Shows all jobs waiting in the verify queue |
*I S,V=volser,E | Inquire on jobs requiring unavaible volser |
*I U | Inquire on output queue for total print lines |
*I U,CL=?,N=ALL | Inquire for total output lines of all josb by class |
*I U,J=xxxx | List output characteristics for a job |
*I U,J=xxxx,CL=?,F=? | Inquire by job for output lines by class and forms |
*I U,J=xxxx,L=?,PG=? | Inquire on output lines and page count for a job |
*I U,Q=HOLD | Inquire on output in hold queue |
*Q,H=N=ALL | Display all jobs on operator hold |
*R device | Restart output on device from beginning |
*R device,G | Repeat data set on printer to print again |
*R device,J | Reprint all complete datasets for job on device |
*R device,RSCD | Restart output; return job to output scheduling |
*R J=xxxx | Restarts a job by jobnumber |
*R RJP,L=LINEnn,I | Restart a BSC line immediately |
*R Rnnnn,device | Restart output on remote printer |
*R Rnnnndevice,G | Repeat data set on printer at remote |
*R S,xxxx | Restart job xxxx during MDS processing |
*R SNARJP,T=Rnnnn,I | Restart a SNA line immediately |
*R SYn,jobname | Restart jobname that is executing on SYn |
*S device | Start local device |
*S device,CP=+n | Increase copy count of data sets for job on device |
*S device,P | Display approx number of lines left to print |
*S device,parms | St output device up for printing as specified |
*S device,R=nn,P | Forward space output on device nn pages |
*S device,RSCD,C | Interrupt device, reschedule, resume printing |
*S device,T | |
*S RJP,L=LINEnn | Start BSC line for RJP processing |
*S Rnnnndevice | Start device at remote |
*S Rnnnndevice,RSCD,C | Interrupt remote device |
*S Rnnnndevice,T | |
*S SNARJP,T=Rnnnn | Start SNA terminal for processing |
*V device,OFFLINE | Vary device offline and terminate the writer |
*V device,online,all | Vary device on or off on all systems |
*V Rnnnndevice,OFFLINE | Vary remote device offline and terminate the writer |
*X RJP | Activate all BSC lines for remote processing |
*X SNARJP | Activate all SNA lines for remote processing |
*Z Rxxxx,message | Send message to a remote |
E CAN,J=jobname,FORCE | To force a job off a system |
*V OPSPR1,ON | Activates the printer. |
Manual IPL Commands..
Generic commands to bring down system
SE 'message to users informing outage '
SE 'message to users informing outage '
TSO STOP
drain initiators...
$PI
P TCPIP
P TN3270E
bring down onlines..
IMS
Xxxx,/che dumpq.
Xxxx,/che purge.
Xxxx,/che freeze.
If ims not going check regions..abdump active regions..still not going thn kill irlm
F imsirlm,abend,nodump
Che=checkpoint
Db2
-prefix stop db2
-prefix start db2
Thread
-prefix dis thd(*)
-prefix can thd(*)
If db2 still exist
F db2irlm,abend,nodump
Mq
Mqmstr
-prefix start qmgr
-prefix stop qmgr
MqChinit
-prefix start chin
-prefix stop chin
Cics
F cicregion,cemt p shut
F cicregion,cemt p shut I
Adabase
Stop adabasename
F dlf,mode=quiesce/drain/normal
P dlf
P vlf
P lla
Automation
AO STOP (AFIRM automation)
P OPSS (OPSMVS/OPSMAIN)
killing JES2
$dline(*)
$pline(line no#)
if jes2 not working then try
$pjes2,abend
Labels:
IPL
JES 2 Resources...
JES2 resource have 15 different buffers which serves specific functionality..Following are the buffer which i came across.... In future post will update more about each buffers....
- BERT - Block Extension reuse tables
- BSCB - Bisynchronous buffers
- BUFX - Extended logical buffers
- CKVR - Checkpoint versions
- CMBS - Console message buffers
- CMDS - Console message buffers used for JES2 commands
- ICES - VTAM® sessions
- LBUF - Logical buffers
- JNUM - Job numbers
- JQES - Job queue elements
- JOES - Job output elements
- NHBS - NJE header/trailer buffers
- SMFB - System management facility buffers
- TGS - SPOOL space/track groups
- TTAB - Trace tables
- VTMB - VTAM buffers
JES2 issues message
$HASP050 to indicate shortage(s) of one or more of the above mentioned buffers.
JES2 resource shortages
might be temporary and occur during periods of heavy utilization or the
shortages might be permanent and impact JES2 processing. Typically, a resource
shortage is the result of not specifying a large enough value for a resource in
your JES2 initialization statements.
$JDHISTORY - Command to display history of resource usage.
Saturday, January 11, 2014
Virtual Lookaside Facility (VLF)
The virtual lookaside facility (VLF) is a set of MVS services that
provide a high-performance alternate path method of retrieving named objects
from DASD on behalf of many users. VLF is designed primarily to improve the
response time for such applications.
VLF uses data spaces to hold data objects in virtual storage as an
alternative to repeatedly retrieving the data from DASD.
VLF keeps objects (for
example Load modules) in Virtual Storage in order to save I/O operations that
would load such objects. Designed primarily to improve performance by
retrieving the most currently used objects from Virtual Storage rather then
performing repetitive I/O operations from DASD.VLF can be configured by using
PARMLIB member COFVLFxx.
Starting VLF
S VLF,SUB=MSTR
Invokes the VLF procedure that starts the
virtual lookaside facility (VLF).
NN=xx
Indicates that the system is to start VLF using
the COFVLFxx member of the logical parmlib or that the system is to start DLF
using the COFDLFxx member of the logical parmlib. In each case, replace xx with
two alphanumeric characters that match the suffix of the parmlib member.
Stopping VLF
P VLF
P VLF
Parm lib
COFVLFxx
CLASS NAME(classname)
{EDSN(dsn1) [VOL(vol)] EDSN(dsn2)...}
{EMAJ(majname1) EMAJ(majname2)...}
[MAXVIRT(nnn)]
Thursday, January 9, 2014
Data Lookaside Facility (DLF)
Data Look
aside Facility (DLF)
DLF is an alternate fast path method of making Dataset available
to many batch jobs faster. Through Hiperbatch, applications can take advantage of
the performance benefits of MVS without changing existing application programs
or the JCL used to run them.
Hiperbatch mainly depends on DLF to access control over expanded
storage.
Initially DLF creats a DLF Object and the user will get
connected to DLF inturn user can access through QSAM or VSAM .The DLF object
exists as long as no users available to use the data/DLF object.Thus we can
have advantage of reduced I/O and faster access to datasets.
Starting
DLF :
S DLF,SUB=MSTR,NN=XX
NN=XX
It indicates which
COFDLFxx parmlib member to use .
Stopping
DLF :
Before stopping DLF we must enter one of the following Modify
command to change its processing to the specified operation.
F DLF,MODE= {DRAIN|D }
{QUIESCE|Q}
{NORMAL|N }
DRAIN
In drain mode, DLF connects the user to existing DLF objects or disconnects the user from DLF/
In drain mode, DLF connects the user to existing DLF objects or disconnects the user from DLF/
QUIESCE
In quiesce mode, DLF only disconnects the user from DLF
objects. No new DLF objects are created while in QUIESCE mode.
NORMAL
In normal mode DLF creates and connects the user to new
DLF objects, connects the user to existing DLF objects,and disconnects the user
from DLF objects.
Once done with Modify command we can go ahead with STOP
command.
P
DLF
Display DLF Status :
F DLF,Status
ParmLib
COFDLFxx
COFDLFxx
The COFDLFxx parmlib member provides the name of the DLF
installation exit and sets limits on the amount of storage that the system can
use for Hiperbatch.
COFDLFxx
CLASS MAXEXPB(megabytes)
[PCTRETB(percent)]
[CONEXIT(exit-name)]
MAXEXPB(nnnn)
MAXEXPB is a required parameter that allows you to
specify, in megabytes, the maximum amount of storage that the system is to use
for Hiperbatch™.
The value for n must be a decimal number from 0 through
9999. You can specify up to 4 digits, including leading zeros. The maximum
value you can specify is the maximum amount of storage that is available on
your system.
Value Range: 0 - 9999 megabytes
PCTRETB(nnn)
PCTRETB is an optional parameter that allows you to
specify the percentage of the storage amount (defined by MAXEXPB) that DLF is
to use for retained DLF objects. Retained DLF objects are used when the output
of one job step is passed to another job or job step.
The value for n must be a decimal number from 0 through
100. You can specify up to 3 digits, including leading zeros. If the value for
n is either not in the range or is not specified, the system uses 0.
Value Range: 0 - 100
Default: 0
CONEXIT(routine-name)
CONEXIT specifies the name of the installation exit routine
for DLF. This routine must be reentrant and reside in an authorized library in
the LNKLST concatenation. For more information about the DLF installation exit
routine.
Subscribe to:
Posts (Atom)