AS/400 integration; SBMITPJOB fails with IDS1005, Address not available due to security policies

If the SBMITPJOB command is used to submit ITP/Server requests from an AS/400, and the SBMITPJOB is unable to connect to the ITP/Server server the request will fail with escape message IDS1005.

The first level text on the IDS1005 escape message explains the error that was returned by OS/400.

It is possible that during an interval of up to 2 minutes all subsequent SBMITPJOB requests will fail with the following IDS1005 escape message for one or more users:

"Failed to connect to ITP/Server name: Address not available".

There are two possible causes for this message:

The network connection was down.
(Resolving network problems falls outside the scope of this Manual.)
There is a TCP/IP port restriction policy configured on the AS/400, causing the user profile that submits the requests to run out of available network ports.

To verify whether or not there is a TCP/IP port restriction policy active, start the CFGTCP command on the AS/400 and select option 4, Work with TCP/IP port restrictions.

The TCP/IP port restrictions control which user profiles are allowed to use the specified TCP/IP port ranges for TCP/IP connections. Unless a port range is not specified in the TCP/IP port restrictions screen this port range can only be used by the specified user profile(s). The TCP/IP protocol specifies that TCP/IP ports have to remain reserved for up to 2 minutes after the connection has been closed, so a restricted AS/400 can run out of TCP/IP ports even if requests are submitted asynchronously.

To resolve this problem, the user profile(s) allowed to run SBMITPJOB have to be allocated sufficient TCP/IP ports for peak operation. This can be accomplished by either assigning ports directly to the user profile(s), by assigning the ports to a shared group profile or by releasing the ports for general use.

The TCP/IP port restrictions ignore adopted authority and only apply the real user profile which owns the running job.