rhunt
Well Known Member
Hello List,
I recently switched out our AS/400 Enterprise Server from a 720 to a 270, and upgraded from V4R5 to V5R2. Because of all the changes in hardware, etc, I have had to re-tune the box. My last problem is with the QZDASOINIT threads and I am hoping to find an AS/400 person out there with suggestions. I have found both all programs within OneWorld open very slowly the first time they are opened and used. Interactive applications take quite a while to open, and the first QBE is very lethargic. However, once you have completed the initial query, you can close the interactive program and re-open it, only to find it opens very quickly and a different query runs exponentially quicker. I have found the same problem with RPT based programs in that the first try takes a very long to to connect to batch versions.
I understand that the first time you open a program, the initial connection can take longer, but our delays are excessive. Also, this problem did not exist in our previous configuration.
I have changed the amount of pre-start threads so I am sure I have available threads waiting for connection. Yet, the delays can still take a very long time.
Does anyone have any tips or tricks that may speed of the connection/performance of QZDASOINIT threads?
Thanks in advance.
Ryan Hunt
I recently switched out our AS/400 Enterprise Server from a 720 to a 270, and upgraded from V4R5 to V5R2. Because of all the changes in hardware, etc, I have had to re-tune the box. My last problem is with the QZDASOINIT threads and I am hoping to find an AS/400 person out there with suggestions. I have found both all programs within OneWorld open very slowly the first time they are opened and used. Interactive applications take quite a while to open, and the first QBE is very lethargic. However, once you have completed the initial query, you can close the interactive program and re-open it, only to find it opens very quickly and a different query runs exponentially quicker. I have found the same problem with RPT based programs in that the first try takes a very long to to connect to batch versions.
I understand that the first time you open a program, the initial connection can take longer, but our delays are excessive. Also, this problem did not exist in our previous configuration.
I have changed the amount of pre-start threads so I am sure I have available threads waiting for connection. Yet, the delays can still take a very long time.
Does anyone have any tips or tricks that may speed of the connection/performance of QZDASOINIT threads?
Thanks in advance.
Ryan Hunt