ISG343I 17.28.56 GRS STATUS 866 S=SYSTEM SYSZMCS ROUTE-GROUP--CNID SYSNAME JOBNAME ASID TCBADDR EXC/SHR STATUS SYSP CONSOLE 0009 00775078 EXCLUSIVE OWN SYSP CONSOLE 0009 00785400 EXCLUSIVE WAIT SYSP CONSOLE 0009 0077C140 EXCLUSIVE WAIT SYSP CONSOLE 0009 008EB830 EXCLUSIVE WAIT SYSP CONSOLE 0009 008EBDE0 EXCLUSIVE WAIT SYSP CONSOLE 0009 00785A90 EXCLUSIVE WAIT SYSP CONSOLE 0009 008EB610 EXCLUSIVE WAIT SYSP CONSOLE 0009 008EB478 EXCLUSIVE WAIT SYSP CONSOLE 0009 008EF590 EXCLUSIVE WAIT SYSP CONSOLE 0009 008EB218 EXCLUSIVE WAIT SYSP CONSOLE 0009 008EF268 EXCLUSIVE WAIT SYSP CONSOLE 0009 008EDB80 EXCLUSIVE WAIT SYSP CONSOLE 0009 008ED960 EXCLUSIVE WAIT SYSP CONSOLE 0009 0076B470 EXCLUSIVE WAIT SYSP CONSOLE 0009 0076B738 EXCLUSIVE WAIT
On Mon, Feb 24, 2014 at 3:53 PM, Jake anderson <[email protected]>wrote: > Can you share your Contention output ? How long is it happening ? Recently > ? > > > On Mon, Feb 24, 2014 at 3:50 PM, baby eklavya <[email protected] > >wrote: > > > It is documented in MVS system Commands manual - under Command Flooding > > section > > > > > > > http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.ieag100%2Fiea2g1b134.htm > > > > We dont have any exits in place to handle commands . But the manuals > states > > only 50 commands can run in console/master address space at a time . So > > obviously it was wrong to run 70 + commands in batch . But even after > > resubmitting the jobs with less than 50 commands at a time later on , it > > was still taking time to complete . > > > > > > > > > > On Mon, Feb 24, 2014 at 3:41 PM, baby eklavya <[email protected] > > >wrote: > > > > > We submitted a batch job having around 60 - 70 vary commands routed > to 3 > > > LPARS using COMMAND statement and we saw that the commands were queued > up > > > for long . A display of GRS contention showed that there was a system > > level > > > enq on SYSZMCS by the console address space . The route commands were > > > processing really slow and we had to remove the commands using CMDS > > REMOVE > > > . > > > > > > Is there a real problem or is this something normal when several route > > > commands are queued for execution ? ,Below is a sample of our CONSOLxx > > > definitions and it is same across each LPAR in the plex . > > > > > > > > > SYSP100 TYPE=MCS STATUS=ACT-SYSP > > > DEFINED=(SYSP) > > > MATCHED=(SYSP) > > > ATTRIBUTES ON SYSP > > > AUTH=(MASTER) CMDSYS=* NBUF=0 > > > DEV=0211 LOGON=OPTIONAL USERID=N/A > > > MFORM=(T,S,J) AREA=(Z) PFKTAB=PFKTAB00 > > > USE=FC DEL=RD RTME=1 RNUM=20 SEG=20 CON=N > > > LEVEL=(ALL) > > > MONITOR=(JOBNAMES) INTIDS=N UNKNIDS=N > > > ROUT=(1-10,12-128) > > > MSCOPE=(*) > > > > > > > > > > > > > > > > > > On Mon, Feb 24, 2014 at 2:19 PM, Jake anderson < > [email protected] > > >wrote: > > > > > >> Ok this for ROUTE Command in CONSOLE.. it would vary from shop to shop > > and > > >> time depends upon the configuration.(CONSOLxx). > > >> > > >> So in your Shop, how long does it takes ? > > >> > > >> > > >> On Mon, Feb 24, 2014 at 1:58 PM, baby eklavya <[email protected] > > >> >wrote: > > >> > > >> > Class C3 commands are ordinary attached commands that run in the > > CONSOLE > > >> > address space . > > >> > > > >> > Such as Route commands > > >> > > > >> > > > >> > On Mon, Feb 24, 2014 at 1:01 PM, R.S. < > [email protected] > > >> > >wrote: > > >> > > > >> > > W dniu 2014-02-24 01:14, baby eklavya pisze: > > >> > > > > >> > > Hello , > > >> > >> > > >> > >> Any idea why MVS class C3 commands take so long to execute . > > >> > >> > > >> > > What is class C3? > > >> > > > > >> > > -- > > >> > > Radoslaw Skorupka > > >> > > Lodz, Poland > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > -- > > >> > > Tre tej wiadomo ci mo e zawiera informacje prawnie chronione > > Banku > > >> > > przeznaczone wy cznie do u ytku s u bowego adresata. Odbiorc mo > e > > by > > >> > > jedynie jej adresat z wy czeniem dost pu osób trzecich. Je eli > nie > > >> > jeste > > >> > > adresatem niniejszej wiadomo ci lub pracownikiem upowa nionym do > > jej > > >> > > przekazania adresatowi, informujemy, e jej rozpowszechnianie, > > >> > kopiowanie, > > >> > > rozprowadzanie lub inne dzia anie o podobnym charakterze jest > > prawnie > > >> > > zabronione i mo e by karalne. Je eli otrzyma e t wiadomo omy > > >> kowo, > > >> > > prosimy niezw ocznie zawiadomi nadawc wysy aj c odpowied oraz > > >> trwale > > >> > > usun t wiadomo w czaj c w to wszelkie jej kopie wydrukowane > > lub > > >> > > zapisane na dysku. > > >> > > > > >> > > This e-mail may contain legally privileged information of the Bank > > >> and is > > >> > > intended solely for business use of the addressee. This e-mail may > > >> only > > >> > be > > >> > > received by the addressee and may not be disclosed to any third > > >> parties. > > >> > If > > >> > > you are not the intended addressee of this e-mail or the employee > > >> > > authorized to forward it to the addressee, be advised that any > > >> > > dissemination, copying, distribution or any other similar activity > > is > > >> > > legally prohibited and may be punishable. If you received this > > e-mail > > >> by > > >> > > mistake please advise the sender immediately by using the reply > > >> facility > > >> > in > > >> > > your e-mail software and delete permanently this e-mail including > > any > > >> > > copies of it either printed or saved to hard drive. > > >> > > > > >> > > mBank S.A. z siedzib w Warszawie, ul. Senatorska 18, 00-950 > > Warszawa, > > >> > > www.mBank.pl, e-mail: [email protected] S d Rejonowy dla m. st. > > >> Warszawy > > >> > > XII Wydzia Gospodarczy Krajowego Rejestru S dowego, nr rejestru > > >> przedsi > > >> > > biorców KRS 0000025237, NIP: 526-021-50-88. Wed ug stanu na dzie > > >> > > 01.01.2014 r. kapita zak adowy mBanku S.A. (w ca o ci wp acony) > > >> wynosi > > >> > > 168.696.052 z ote. > > >> > > > > >> > > > > >> > > > > ---------------------------------------------------------------------- > > >> > > For IBM-MAIN subscribe / signoff / archive access instructions, > > >> > > send email to [email protected] with the message: INFO > > >> IBM-MAIN > > >> > > > > >> > > > >> > > ---------------------------------------------------------------------- > > >> > For IBM-MAIN subscribe / signoff / archive access instructions, > > >> > send email to [email protected] with the message: INFO > > IBM-MAIN > > >> > > > >> > > >> ---------------------------------------------------------------------- > > >> For IBM-MAIN subscribe / signoff / archive access instructions, > > >> send email to [email protected] with the message: INFO > IBM-MAIN > > >> > > > > > > > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
