×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Ok, the issue turned out to be a bad SQL package. The following work
around suggested by IBM worked great:
http://www-01.ibm.com/support/docview.wss?uid=nas186256a81004eff5c86256ff500732959
After reading all this, does anyone think it a bad idea to generally just
run the following after an OS upgrade when you have the system in a
restricted state (like after ptf's but before a final SAVSYS for the new
upgrade)?
DLTSQLPKG QGPL/QZDAPKG
<snip>
One thing you could try while we wait for a response from development is
to delete QGPL/QZDAPKG. That has solved some UPS WorldShip problems in the
past. It gets recreated automatically when the DB host server is started.
To restart the database host server jobs without disrupting users, you
should verify that no one is using the QZDASOINIT jobs.
To delete the package file and restart the database host server jobs, you
should run the following commands and press the Enter key:
ENDHOSTSVR *DATABASE
ENDPJ SBS(QUSRWRK) PGM(QSYS/QZDASOINIT) OPTION(*IMMED)
ENDPJ SBS(QUSRWRK) PGM(QSYS/QZDASSINIT) OPTION(*IMMED)
ENDPJ SBS(QSERVER) PGM(QSYS/QZDAINIT) OPTION(*IMMED)
WRKOBJ OBJ(QGPL/QZDAPKG) Take option 4 to delete.
STRHOSTSVR *DATABASE
STRPJ QSERVER QZDAINIT
Restart the UPS World Ship application and retest..
</snip>
Rob Berendt
midrange.com
