This idea was previously posted on discussion forums.

Whilst investigating the RDi Web Services wizard for RPG code I noticed the ability to abstract the connection to the iSeries using a J2C connection factory - see topic "Developing i5/OS Web services" in the RDi help files. This allows one to delegate the management of the connection, including server name and authentication details to Websphere and not have to build this into the application. It also gives us the ability to provide connection pooling, monitoring and so on.

The current method we have of using runtime linkage parts means that we still need to update server settings in a properties file before moving the application between development, test, production etc. servers. It also means that we need to develop our own means of setting, storing and retrieving user credentials to supply to sysLib.setRemoteUser()

Is there any way that the existing CALL statements could use a connection factory to manage the connection to the remote system?

From one reply to the original discussion I realise that this is one of many possible solutions but I think has merit in that it essentially makes the iSeries connection available as a container managed resource in the same way that DataSources are.