> We run 1 job at a time which allocates 24 tape drives. Can you expand on that? For instance, we would run one volume dump job for each volume. Then I had 6 drives available and set as the DeviceLimit. Then I allowed 7 connections per drive. So Exhpdm would support a total of 6x7=42 connections. Then I would normally run these jobs in a JES class set aside just for this process which had 42 open initiators.
So, if any one of those changes I can get varied results.... More inits open would have Exhpdm issue wait messages (but should not slow down the process) Less inits open would mean I'm not maximizing my thruput. No messages, but it would run slower. More drives would simply be ignored. Less drives would lessen my thruput and cause wait messages since I'd still have 42 jobs that want to connect. There is also the issue of how fast the disk can serve up the data - although this is outside the control of your Exhpdm processes. Were there disk channels unavailable during the process? Do you normally get the wait messages? If not, then is has to be something in the setup as I've described above. I found it useful to set the processes up so I did not normally get the wait message - then they become an indicator that something changed. Jeffrey Deaver, Engineer, Systems Engineering 651-665-4231 ---------------------------------------------------------------------- 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
