Our trans DL68 often processes a long time, but not every time like this, and we use CEMT to trace it fond the transaction spend on ZCIOWAIT + DFHZARR1. This transaction is used to connect CICS TS v3.1.2 and IBM P550, and send request by CALL 'CMINIT' 'CMALLC' 'CMSEND' 'CMRCV' statments. I paste some screen. But now I do know how to find what resource that the transaction is waiting, and how to resolution. If anybody have any ideas, can help us. Below are some dumps from TMON and CEMT Some trans are running a long time DATE TIME JOBNAME TRANID TASK# TERMID RESP CPU PAGING FILEIO 03/28 00:01:09 CICSA DL68 78084 22.9606 0.0070 0 16 03/28 00:01:13 CICSA DL68 78403 0.3814 0.0080 0 17 03/28 00:01:13 CICSA DL68 78410 0.2672 0.0074 0 17 03/28 00:01:13 CICSA DL68 78417 0.1192 0.0079 0 17 03/28 00:01:13 CICSA DL68 78418 0.0971 0.0077 0 17 03/28 00:01:14 CICSA DL68 78422 0.7969 0.0459 0 125 The waitting type is ZCIOWAIT RES TYPE RES NAME WT CNT WT TIME % OF RESPONSE * * * * <------------------> CHANGE PRIORITY 1 0.0003 0.00 SWITCH TCB 32 0.0805 0.35 WAIT FOR REDSPTCH 34 0.0850 0.37 ZCIOWAIT 1 22.8415 99.48 1ST DISPATCH 1 0.0003 0.00 From CEMT, we know the transaction DL68 is waitting for ZCIOWAIT + DFHZARR1, DLOU0E include CALL 'CMINIT' 'CMALLC' 'CMSEND' 'CMRCV' statments and it's linked by DL68.
Task(0051759) Tranid(DL68) Facility() Runstatus(Suspended) Ftype(Task) Priority( 200 ) Purgetype( ) Startcode(SD) Userid(DUUSER) Uow(C7817E40876A5FC4) Htype(ZCIOWAIT) Hvalue(DFHZARR1) Htime(000035) Indoubt(Backout) Indoubtwait(Wait) Bridge() Identifier() Indoubtmins(000000) Uow(C7817E40876A5FC4) Htype(ZCIOWAIT) Hvalue(DFHZARR1) Htime(000035) Indoubt(Backout) Indoubtwait(Wait) Bridge() Identifier() Indoubtmins(000000) Db2plan(PLANDL) Activity() Activityid() Process() Processtype() Tcb(Qr) Brfacility(0000000000000000) Currentprog(DLOU0E) At 2011-03-03 05:55:15，"Pearce, Colin E" <[email protected]> wrote: >Yes exactly, I thought Tmon would display this Resource Type and Resource >Name. > > >Thanks > > > >Colin Pearce > > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of >Chase, John >Sent: Thursday, March 03, 2011 1:03 AM >To: [email protected] >Subject: Re: ZCIOWAIT message > >> -----Original Message----- >> From: IBM Mainframe Discussion List On Behalf Of Pearce, Colin E >> >> Hi, >> >> While I don't have access to Tmon, I am amazed that it doesn't display >the Dispatcher Task Summary >> Table the same as Omegamon does. This display is fundamental to any >CICS monitor as this gives a list >> of all the tasks that are currently dispatched. This table displays >all the Tasks currently dispatched >> in CICS (both System and User) and both the Resource type and Resource >name for each task. These two >> 8 byte fields are taken from each Tasks DTA (Dispatcher Task Area) and >> these live in the Dispatcher Domain. > >You mean something like this? > >JOBNAME: CICSTEST ACTIVE TASKS >RESOURCE(ALL TASKS) >APPLID : CICSTEST H SYS: SYSA CSM: TMONCICS V=L > >COMMAND: CYCLE: >MMSS > > > _EVENT _WLM >_VNXT? >_SORTKEYS DISPLAY ORDER: SA (2ND POS. A=ASCENDING >D=DESCENDING) > TRAN TASK PAGE TOTAL-CPU TOT-IO STG CUR-WAIT RES-TYPE RES-NAME >RSTA > * * * > >_ CSNE 00075 8 .0863 0 4,960 1:20.434 ZC DFHZNAC1 >SUSP >_ COIE 00079 0 10.2812 0 52,192 12.4911 USERWAIT EMSTATUS >MVS >_ DTCN 00587 0 .0267 100 68,472 18.3439 ZCIOWAIT DFHZARQ1 >SUSP > >This is from TMON/CICS option 1.1, "Resource" view. > > -jc- > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, send email to >[email protected] with the message: GET IBM-MAIN INFO Search the archives >at http://bama.ua.edu/archives/ibm-main.html > >---------------------------------------------------------------------- >This message w/attachments (message) is intended solely for the use of the >intended recipient(s) and may contain information that is privileged, >confidential or proprietary. If you are not an intended recipient, please >notify the sender, and then please delete and destroy all copies and >attachments, and be advised that any review or dissemination of, or the taking >of any action in reliance on, the information contained in or attached to this >message is prohibited. >Unless specifically indicated, this message is not an offer to sell or a >solicitation of any investment products or other financial product or service, >an official confirmation of any transaction, or an official statement of >Sender. Subject to applicable law, Sender may intercept, monitor, review and >retain e-communications (EC) traveling through its networks/systems and may >produce any such EC to regulators, law enforcement, in litigation and as >required by law. >The laws of the country of each sender/recipient may impact the handling of >EC, and EC may be archived, supervised and produced in countries other than >the country in which you are located. This message cannot be guaranteed to be >secure or free of errors or viruses. > >References to "Sender" are references to any subsidiary of Bank of America >Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are >Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a >Condition to Any Banking Service or Activity * Are Not Insured by Any Federal >Government Agency. Attachments that are part of this EC may have additional >important disclosures and disclaimers, which you should read. This message is >subject to terms available at the following link: >http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you >consent to the foregoing. > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: GET IBM-MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html
