Passing Global Shell variables to awk Post: 302847169

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Passing shell variables to awk program..

Hello, Can we pass shell variables like $PATH etc. to a awk program part for example, awk ' { fieldValue=$PATH .... }' file

2. Shell Programming and Scripting

Passing awk Variables

I am trying to pass the results from a variable gathered from awk, however when I echo the 'PARSE' and 'SUB', the response is blank. This is my command. awk -F= '/Unit/''{ PARSE=substr($2,1,5) ; SUB=substr($2,1,1) }' inputfile.lst Is this a kind of valid attempt or am I obligated to declare...

3. UNIX for Dummies Questions & Answers

How to declare global variables for shell script

Hi, I do have some variables accessed in more than one script. I want to have those variables in a command file anduse them. Something like a header file that we use in C programs. I dont want to set them as environment variables. Is there any other option, like header file in scripting ?? ...

4. Solaris

How to access ENV variables of non global zones in global zone???

Hi Guys, My requirement is I have file called /opt/orahome/.profile in non global zone. PATH=/usr/bin:/usr/ucb:/etc:/usr/sbin:/usr/local/bin:/usr/openwin/bin:. export PATH PS1="\${ORACLE_SID}:`hostname`:\$PWD$ " export PS1 EDITOR=vi export EDITOR ENV=/opt/orahome/.kshrc export ENV...

5. UNIX for Dummies Questions & Answers

Passing Shell Variables to an awk command

Hello, I have two files File1 & File2. File1 76 135 136 200 250 345 .... File2 1 24 1 35 1 36 1 72 .... I want to get all the values form File2 corresponding to the range in File 1 and feed it to a program. Is the code below right? Can I pass shell variables to awk in this...

6. Shell Programming and Scripting

Passing awk variables to shell

Hi. I need to parse file and assign some values to variables, right now i do like below MYHOMEDIR=`awk '/Home/ {print $NF}' output.txt` MYSHELL=`awk '/Shell/ {print $NF}' output.txt` PRGRP=`awk '/Primary/ {print $NF}' output.txt` SECGRP=`awk '/Second/ {print $NF}' output.txt` In this...

7. Shell Programming and Scripting

ksh passing to awk multiple dyanamic variables awk -v

Using ksh to call a function which has awk script embedded. It parses a long two element list file, filled with text numbers (I want column 2, beginning no sooner than line 45, that's the only known thing) . It's unknown where to start or end the data collection, dynamic variables will be used. ...

8. Shell Programming and Scripting

Problem in Global variables in shell script

hi, i have a shell script which calls another shell which in turn calls another shell script. Main_shell_script.sh echo "In Main_shell_script.sh" FILENAME="original.txt" # LINE 1 DST_FILENAME=$FILENAME # LINE 2 echo "FILENAME = {$FILENAME}" echo "DST_FILENAME =...

9. Shell Programming and Scripting

Passing awk variables to bash variables

Trying to do so echo "111:222:333" |awk -F: '{system("export TESTO=" $2)}'But it doesn't work

10. Shell Programming and Scripting

Awk: passing shell variables through and extracting text

Hello, new to the forums and to awk. Glad to be here. :o I want to pass two shell (#!/bin/sh) variables through to awk and use them. They will determine where to start and stop text extraction. The code with the variables hard-coded in awk works fine; the same code, but with the shell...

LEARN ABOUT OPENDARWIN

history

history(n)						       Tcl Built-In Commands							history(n)

__________________________________________________________________________________________________________________________________________________

NAME

       history - Manipulate the history list

SYNOPSIS

       history ?option? ?arg arg ...?
_________________________________________________________________

DESCRIPTION

       The  history  command  performs	one of several operations related to recently-executed commands recorded in a history list.  Each of these
       recorded commands is referred to as an ``event''.  When specifying an event to the history command, the following forms may be used:

       [1]    A number:  if positive, it refers to the event with that number (all events are numbered starting at 1).	If the number is negative,
	      it  selects an event relative to the current event (-1 refers to the previous event, -2 to the one before that, and so on).  Event 0
	      refers to the current event.

       [2]    A string:  selects the most recent event that matches the string.  An event is considered to match the string either if  the  string
	      is the same as the first characters of the event, or if the string matches the event in the sense of the string match command.

       The history command can take any of the following forms:

       history
	      Same as history info, described below.

       history add command ?exec?
	      Adds  the  command argument to the history list as a new event.  If exec is specified (or abbreviated) then the command is also exe-
	      cuted and its result is returned.  If exec isn't specified then an empty string is returned as result.

       history change newValue ?event?
	      Replaces the value recorded for an event with newValue.  Event specifies the event to replace, and defaults  to  the  current  event
	      (not  event  -1).  This command is intended for use in commands that implement new forms of history substitution and wish to replace
	      the current event (which invokes the substitution) with the command created through substitution.  The  return  value  is  an  empty
	      string.

       history clear
	      Erase the history list.  The current keep limit is retained.  The history event numbers are reset.

       history event ?event?
	      Returns the value of the event given by event.  Event defaults to -1.

       history info ?count?
	      Returns  a formatted string (intended for humans to read) giving the event number and contents for each of the events in the history
	      list except the current event.  If count is specified then only the most recent count events are returned.

       history keep ?count?
	      This command may be used to change the size of the history list to count events.	Initially, 20 events are retained in  the  history
	      list.  If count is not specified, the current keep limit is returned.

       history nextid
	      Returns  the number of the next event to be recorded in the history list.  It is useful for things like printing the event number in
	      command-line prompts.

       history redo ?event?
	      Re-executes the command indicated by event and return its result.  Event defaults to -1.	This command results in history  revision:
	      see below for details.

HISTORY REVISION

       Pre-8.0 Tcl had a complex history revision mechanism.  The current mechanism is more limited, and the old history operations substitute and
       words have been removed.  (As a consolation, the clear operation was added.)

       The history option redo results in much simpler ``history revision''.  When this option is invoked then the most recent event  is  modified
       to  eliminate  the  history  command and replace it with the result of the history command.  If you want to redo an event without modifying
       history, then use the event operation to retrieve some event, and the add operation to add it to history and execute it.

KEYWORDS

       event, history, record

Tcl																	history(n)