<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: trace in csh in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152879#M455020</link>
    <description>Thanks for your reply. &lt;BR /&gt;&lt;BR /&gt;It is not a choice using csh, but SAP's option.&lt;BR /&gt;&lt;BR /&gt;I have alredy looked at faqs.org, but did not find anything.&lt;BR /&gt;&lt;BR /&gt;In the man too. Could you, please, pinpoint the command or the question ?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Jose</description>
    <pubDate>Tue, 27 Jan 2009 16:00:06 GMT</pubDate>
    <dc:creator>Jose_C_Moraes</dc:creator>
    <dc:date>2009-01-27T16:00:06Z</dc:date>
    <item>
      <title>trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152877#M455018</link>
      <description>Hi, I need help.&lt;BR /&gt;&lt;BR /&gt;Does anyone know if there is a similar csh command similar to the sh trace command set -x?&lt;BR /&gt;&lt;BR /&gt;TIA, regards&lt;BR /&gt;Jose</description>
      <pubDate>Tue, 27 Jan 2009 15:35:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152877#M455018</guid>
      <dc:creator>Jose_C_Moraes</dc:creator>
      <dc:date>2009-01-27T15:35:46Z</dc:date>
    </item>
    <item>
      <title>Re: trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152878#M455019</link>
      <description>Hi Jose:&lt;BR /&gt;&lt;BR /&gt;Yes, you have this one and others for tracing:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B2355-60130/csh.1.html" target="_blank"&gt;http://docs.hp.com/en/B2355-60130/csh.1.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Of course, use 'csh' at your own risk :-)&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/" target="_blank"&gt;http://www.faqs.org/faqs/unix-faq/shell/csh-whynot/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 27 Jan 2009 15:50:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152878#M455019</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-01-27T15:50:52Z</dc:date>
    </item>
    <item>
      <title>Re: trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152879#M455020</link>
      <description>Thanks for your reply. &lt;BR /&gt;&lt;BR /&gt;It is not a choice using csh, but SAP's option.&lt;BR /&gt;&lt;BR /&gt;I have alredy looked at faqs.org, but did not find anything.&lt;BR /&gt;&lt;BR /&gt;In the man too. Could you, please, pinpoint the command or the question ?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Jose</description>
      <pubDate>Tue, 27 Jan 2009 16:00:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152879#M455020</guid>
      <dc:creator>Jose_C_Moraes</dc:creator>
      <dc:date>2009-01-27T16:00:06Z</dc:date>
    </item>
    <item>
      <title>Re: trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152880#M455021</link>
      <description>Hi (again) Jose:&lt;BR /&gt;&lt;BR /&gt;Add the '-x' to your shell interpreter (shebang) line, like this:&lt;BR /&gt;&lt;BR /&gt;#!/usr/bin/csh -x&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Tue, 27 Jan 2009 16:17:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152880#M455021</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2009-01-27T16:17:47Z</dc:date>
    </item>
    <item>
      <title>Re: trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152881#M455022</link>
      <description>Thanks, James.&lt;BR /&gt;&lt;BR /&gt;But there is no way to trace just a few lines in a script, like set -x and set +x in posix ?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Jose</description>
      <pubDate>Tue, 27 Jan 2009 16:43:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152881#M455022</guid>
      <dc:creator>Jose_C_Moraes</dc:creator>
      <dc:date>2009-01-27T16:43:33Z</dc:date>
    </item>
    <item>
      <title>Re: trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152882#M455023</link>
      <description>from the "man" page regarding "builtin variables"&lt;BR /&gt;&lt;BR /&gt;"echo"&lt;BR /&gt;This variable is set by the -x command line option. If set, all built-in commands and their arguments are echoed to the standard output device just before being executed. Built-in commands are echoed before command and file name substitution, since these substitutions are then done selectively. For non-built-in commands, all expansions occur before echoing."&lt;BR /&gt;&lt;BR /&gt;i believe that "setenv echo..." and "unset echo" may get you what you want</description>
      <pubDate>Tue, 27 Jan 2009 17:20:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152882#M455023</guid>
      <dc:creator>OldSchool</dc:creator>
      <dc:date>2009-01-27T17:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152883#M455024</link>
      <description>&lt;!--!*#--&gt;&amp;gt; i believe that "setenv echo..." [...]&lt;BR /&gt;&lt;BR /&gt;Wouldn't you think that "setenv" is a bit of&lt;BR /&gt;overkill for something which only this shell&lt;BR /&gt;cares about?  "man csh" suggests that&lt;BR /&gt;something like:&lt;BR /&gt;      set echo = 1&lt;BR /&gt;or:&lt;BR /&gt;      set verbose = 1 # For "-v"&lt;BR /&gt;would work.&lt;BR /&gt;&lt;BR /&gt;One easy way to find out...</description>
      <pubDate>Tue, 27 Jan 2009 17:43:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152883#M455024</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2009-01-27T17:43:01Z</dc:date>
    </item>
    <item>
      <title>Re: trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152884#M455025</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;don't use 'setenv echo' - do it like this:&lt;BR /&gt;&lt;BR /&gt;...&lt;BR /&gt;set echo&lt;BR /&gt;...&lt;BR /&gt;foreach var (a b c)&lt;BR /&gt;echo $var&lt;BR /&gt;end&lt;BR /&gt;...&lt;BR /&gt;unset echo&lt;BR /&gt;...&lt;BR /&gt;&lt;BR /&gt;This will trace only the lines between the 'set echo' and 'unset echo'.&lt;BR /&gt;&lt;BR /&gt;mfG Peter&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Jan 2009 18:09:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152884#M455025</guid>
      <dc:creator>Peter Nikitka</dc:creator>
      <dc:date>2009-01-27T18:09:00Z</dc:date>
    </item>
    <item>
      <title>Re: trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152885#M455026</link>
      <description>If SAP uses csh (BTW: for the login shell only) this should not prevent you from using ksh for your scripts. In fact, if you use the standard installation procedure, all profiles are created as (k)sh and csh versions. Look for any .??*env* in SIDadm's home! Just make sure your script starts with "#!/usr/bin/ksh" and are executable, source the according env file and everything will work fine.&lt;BR /&gt;&lt;BR /&gt;On the other hand, if you want to trace/debug an existing script, you have no choice.&lt;BR /&gt;&lt;BR /&gt;My 2 cents,&lt;BR /&gt;Armin&lt;BR /&gt;</description>
      <pubDate>Wed, 28 Jan 2009 09:21:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152885#M455026</guid>
      <dc:creator>Armin Kunaschik</dc:creator>
      <dc:date>2009-01-28T09:21:30Z</dc:date>
    </item>
    <item>
      <title>Re: trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152886#M455027</link>
      <description>Sorry, I am out of town, will be back tomorrow to do the tests&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Jose</description>
      <pubDate>Wed, 28 Jan 2009 13:38:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152886#M455027</guid>
      <dc:creator>Jose_C_Moraes</dc:creator>
      <dc:date>2009-01-28T13:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152887#M455028</link>
      <description>Hi Armin&lt;BR /&gt;&lt;BR /&gt;It is only the login shell. All of the others are posix shell.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Jose</description>
      <pubDate>Thu, 29 Jan 2009 12:47:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152887#M455028</guid>
      <dc:creator>Jose_C_Moraes</dc:creator>
      <dc:date>2009-01-29T12:47:51Z</dc:date>
    </item>
    <item>
      <title>Re: trace in csh</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152888#M455029</link>
      <description>The suggested trace works fine.&lt;BR /&gt;&lt;BR /&gt;Thanks you all for the help.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Jose</description>
      <pubDate>Thu, 29 Jan 2009 12:49:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/trace-in-csh/m-p/5152888#M455029</guid>
      <dc:creator>Jose_C_Moraes</dc:creator>
      <dc:date>2009-01-29T12:49:07Z</dc:date>
    </item>
  </channel>
</rss>

