Willie, I agree with Jeffrey's thoughts for you so far with your ExHPDM problem.
You need to take a look at the ExHPDM address space log, to see what else might have occurred to cause the delay in a stream task from being started. The things to look for are that perhaps due to other workload on the system a tape device could not be allocated causing the stream task to be delayed. If your ExHPDM parameters specify that the allocation is to WAIT either via the STREAM definition, or it has been specified in the DD SUBSYS parameters in your job(s), or it has been defaulted, then the client connection waits until the stream task request is redriven by a subsequent connection initiation or a current connection termination. It is either of these conditions that causes a new stream task to be started and an available tape drive to be allocated. I suspect that it is probably this situation in this case that has caused the client connection to have not been serviced within the timeframe that you expected. If indeed this is the case, then a solution for you might be to dedicate a certain number of tape devices specifically for ExHPDM workload, or to specify a RETAIN period on the DEVICE statement in the ExHPDM parameters that then ensures that any other ExHPDM work, continues to be serviced by the already started stream. Now, if you decide to make use of the RETAIN parameter in the DEVICE statement, and you are running ExHDPM V3.1 or ExHPDM V6.1 that provides support for our T10K tape devices, then you will also need to have applied PTF L1P1008 (ExHDPM V3.1) or L1P1009 (ExHPDM V6.1), which ensures that after the RETAIN time expiration, that the device is unallocated. Anyway, I hope this assist you in determining the cause of the problem. Let me know how else I can assist. Cheers Luis Monge Advisory Software Engineer ExHPDM Development Data Management Group Australian Software Research and Development Centre Sun Microsystems Email: [EMAIL PROTECTED] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of willie bunter Sent: Thursday, 19 October 2006 10:20 PM To: [email protected] Subject: EXHPDM - QUESTION Last night one of our backup batch jobs too about 5 hours to complete as opposed to the normal 1 hour 20 minutes. I checked the job but all looks okay. I noticed that the following messages appears for various stream tasks. Here is one of them.: SOV06045I Connection ID 1183 for DD TAPE26 from JOB:GPRX0B01.GPRX0B10 is waiting SOV06204I Write client JOB:GPRX0B01.GPRX0B10, DSN PROD1.EXPL.J01S999.SOVDSSU.GPR uniquifier BF934A2D1F531549 started 19OCT2006 03:30:43, ended 19OCT2006 03:45:50, elapsed 00:15:07 total blocks 3203, I/O time 205.482, delayed 625.343 ( 68.9%) avg kB/sec 925, I/O utilization 22.6% I checked the SOV06045I message which says : "The specified connection is waiting for a stream task to become available because the connection has WAIT(YES) specified (or defaulted) and no stream task is currently able to process the connection." I am not sure why this would be? Can anybody tell me the reason why a stream task is not available? Could I have missed something? Thanks in advance. --------------------------------- Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
