I would recommend investigate into the QZDASOINIT jobs as follow:
- Force debug messages by setting parameter MESSAGES_DEBUG to *YES in the qaqqini file
- Force the joblog to print by temporarily changing the job description.
The joblog will show you the SQL used, how much time every statement taken, and the access plan (How did SQL planned to get the records).
Dig deeper on Physical connections to iSeries
Related Q&A from Shahar Mor
Use work station customize object or printer type in iSeries Access to print the output of an RPG file from the AS/400 to an HP printer.continue reading
Use the the iSeries QSYSOPR message to look for any errors in passwords when running a program on the iSeries that transfers data to a spreadsheet on...continue reading
Connecting the iSeries in AS/400, issue STRHOSTSVR *ALL. Make sure the as-signon port is in listen state and check the firewall settings.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.