What changes were made to your memory config? xstor, cstor, mdc size ? Any changes to the I/O configuration?
Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." ________________________________ From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of TaeMin Baek Sent: Monday, May 17, 2010 3:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] Batch job takes too long in OS/390 Guest under z/VM v6.1 We migrate three OS/390 system from 2064-2C1 running on native LPAR mode to 2098-T01 running under z/VM like the below. HW: z10 BC- 2098 T01 (GCP 1 EA) OS: z/VM V6.1 Guest OS: Four OS/390 v2.10 (SE02, SE05, SE06, CF) running under z/VM 1) Between three OS/390 guests share many DASD which are defined by full-pack minidisk in CP directory. 2) three OS/390 guests share the DASD using GRS. MIM is used before migration 3) three OS/390 guests are coupled by Sysplex(VCFLINK under z/VM) thru CF guest 4) Sysplex(XCF) is used for only GRS and Tape sharing. MIA is used before migration 5) GRS was not used befor migration * Problem Symptom => During night time, batch job workload on SE02 was taking too long and SE02 Guest system has high CPU usage(Specially Supervisor CPU% is high around 32% and Emulated CPU% is 35%) and I/O wait(12%) by performance toolkit. => By monitoring in OS/390(SE02), CPU Usage of MASTER, GRS, CATALOG task is high. therefore batch job is hard to get CPU resource. => CF Guest user has only 1% of CPU utilization. => batch job use DASD and Tape devices. could it be caused by VM side or OS/390? What do we need to check more to find what is root cause and to fix this problem?
