×
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.
Someone I know had a resource conflict during STRTCP after a V5R3 -->
V5R4 upgrade, the actual problem was apparently the QSYSARB5 job holding
a lock on QUSRSYS/QTCPACT of type X'19EF'
One of IBM's recommendations was to "change the IPL attribute (CHGIPLA)
to not start TCP and add a STRTCP to QSTRUP."
From the SL analyst:
"I would suspect the new release has affected the startup timing
just enough to cause misc. issues on startup.
...the IPL attribute is only recommended to be set to start
TCP/IP in a very vanilla environment. If you have anything more
complex, which you do,
the recommendation is to not start TCP/IP with the IPL attribute
but rather start it in QSTRUP."
In this day and age does anyone really have a "very vanilla
environment?" I spent a lot of time a few years back getting
STRTCP(*YES) to work properly so that it wasn't starting twice and
creating miscellaneous server conflicts. I'm curious what everyone else
thinks and does.
Regards,
Scott Ingvaldson
Senior IBM Support Specialist
Midwest Region Data Center
Fiserv.
midrange.com
