<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Clovertech | John Perks | Activity</title>
	<link>https://clovertech.infor.com/members/john-perks/activity/</link>
	<atom:link href="https://clovertech.infor.com/members/john-perks/activity/feed/" rel="self" type="application/rss+xml" />
	<description>Activity feed for John Perks.</description>
	<lastBuildDate>Sat, 18 Apr 2026 10:10:49 -0400</lastBuildDate>
	<generator>https://buddypress.org/?v=</generator>
	<language>en-US</language>
	<ttl>30</ttl>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
	
						<item>
				<guid isPermaLink="false">795abc9b1930ce628bb8c35ef3835c54</guid>
				<title>John Perks replied to the topic output_cycle problem in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/output_cycle-problem/#post-74274</link>
				<pubDate>Thu, 05 May 2011 19:04:21 -0400</pubDate>

									<content:encoded><![CDATA[<p>That was it.<br />
Since the thread was UPOC protocol, not fileset-local, the PROTOCOL.IBDIR was not available and I had done a cd to a different directory in one of the tcl procs. &nbsp;That changed it immediately for the process&#8217; command thread, and the rest is academic.</p>
<p>Thanks.</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">0009f943c8f16da9e2de7a54a5dbd58e</guid>
				<title>John Perks replied to the topic Call a seperate tcl proc from a different file in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/call-a-seperate-tcl-proc-from-a-different-file/#post-68119</link>
				<pubDate>Thu, 04 Jun 2009 20:44:09 -0400</pubDate>

									<content:encoded><![CDATA[<p>Jim&#8217;s methods are not mutually exclusive, by the way.<br />
They all could be utilized to some degree, depending on the needs of your situation.<br />
#2 is probably the easiest to implement in terms of coding changes. &nbsp;You can easily put the duplicated code into a called proc and just remember to globalize the necessary variables.<br />
But that called proc&hellip;<span class="activity-read-more" id="activity-read-more-15793"><a href="https://usspvlclovertch2.infor.com/forums/topic/call-a-seperate-tcl-proc-from-a-different-file/#post-68119" rel="nofollow ugc">Read more</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
		
	</channel>
</rss>