<div>
Sorry, as an update we've been doing savrstobj and not savrstlib.
</div>


<div>
Hi Gary, thanks for getting back to me. Give me a day or so to get you all that information. <br />
<br />
Thanks. <br />
<br />
Anthony
</div>


<div>
Our issue ended up being outside the scope of the actual commands and the 400 itself and was instead the physical connection between the two locations.
</div>


<div>
<div class="content wysiwyg-content">
We are currently trying to use the savrstlib command between our source and target iSeries systems. &nbsp;The transfer happens successfully; however, on the source system we need to kill the job otherwise we cannot access the files on the target system. &nbsp;Is there a reason why the job wouldn't end on the source system if it is actually successful considering we checked the data on the target system upon killing the job?<br />
<br />
Any help on this would be greatly appreciated.<br />
<br />
-Anthony
</div>
</div>


We are currently trying to use the savrstlib command between our source and target iSeries systems.  The transfer happens successfully; however, on the source system we need to kill the job otherwise we cannot access the files on the target system.  Is there a reason why the job wouldn't end on the source system if it is actually successful considering we checked the data on the target system upon killing the job?

Any help on this would be greatly appreciated.

-Anthony

Sorry, as an update we&amp;#39;ve been doing savrstobj and not savrstlib.

Hi Gary, thanks for getting back to me. Give me a day or so to get you all that information. 

Thanks. 

Anthony

Our issue ended up being outside the scope of the actual commands and the 400 itself and was instead the physical connection between the two locations.

Savrstlib Not Releasing After Job Completed on Source System

We are currently trying to use the savrstlib command between our source and target iSeries systems.  The transfer happens successfully; however, on the source system we need to kill the job otherwise we cannot access the files on the target system.  Is there a reason why the job wouldn&amp;#39;t end on the source system if it is actually successful considering we checked the data on the target system upon killing the job?

Any help on this would be greatly appreciated.

-Anthony

IBM i, formerly known as AS/400, is a proprietary, midrange, object-based operating and application system. It includes a relational database, a menu-driven interface, support for multiple users, block-oriented terminal support and printers, and supports security, communications, and web-based application servers including Websphere, Apache and Tomcat.