Yes, USR0340N can be used for this purpose. I’ve written a simple wrapper subprogram for some clients that would accept the library name and create an RPC request to call that wrapper to flush the buffer pool for that library and/or program.
If you are using the local buffer pool and have NTASKS greater than 1, you should modify the NTOS parameter LBPNAME to a non-blank value. This will allow all your instances of the RPC server in that job to share the same local buffer pool. Otherwise you would have to call the USR0340N routine repeatedly until all tasks had flushed…not a very deterministic solution. I haven’t found any reason yet to not share the LBP within an RPC server.
Another option is to use the global buffer pool and have the RPC Servers use it. If you migrate your programs in an online environment that shares the same GBP as the RPC servers, they will immediately have the new version available to them.
#webMethods#Mainframe-Integration#EntireX