Experts Heaven

Welcome back!

This script will be useful if you require to split a huge file based on number of lines or records. Normal file splitters available in the market split the file based on the size (byte, KB, MB) which cannot be used to split based on number of lines or records.

Steps to use the script:

1. Save the below script as lsplit.ksh
propDIR=./
propFile=$propDIR/SSNRange.txt.prop
inpFile=$1
date
startLineNo=1
count=1
while read line
do
startLineNo=`echo $line | cut -f1 -d,`
endLineNo=`echo $line | cut -f2 -d,`
if [ "$endLineNo" != "" -a "$startLineNo" != "" ]; then
echo "Cut here from $startLineNo to $endLineNo"
sed -n "$startLineNo","$endLineNo"p $inpFile > $inpFile.split.$count
count=`expr $count + 1`
fi
done < $propFile
date


2. Create a properties file SSNRange.txt.prop which would contain the range of records or lines. Example of properties file is as follows
1,400
401,1504
1505, 7000

3. Run the script
$ lsplit.ksh infile.txt

4. Three output files will be created

• infile.txt.split.1 –> Creates a file with first 400 lines
• infile.txt.split.2 –> Creates a file with lines starting from 401 to 1504
• infile.txt.split.3 –> Creates a file with lines starting from 1505 to 7000

Advantages of this script:

• File is split based on line numbers are records.
• No manual editing is required the correct the first and last records
• Easy to handle it in batch

Courtesy: Santhosh Fabian

Unique visitors to post: 90

Finally have found out a way to terminate the telnet session with out killing the foreground process which is running. Anyone struck with the above situation can follow this

Assume a script “script1″ is running in the foreground for a long time and this script needs to be retained even if the telnet session is closed. Here are the steps which needs to be followed.

1. On the telnet screen press <CTRL + Z>. This will temporarily stop the script or process to run.

$ ./script1.ksh
[1] + Stopped (SIGTSTP)        ./script1.ksh

2. Type in the command “bg” to run the process in background

$ bg
[1]     ./script1.ksh&

3. Identify the session process ID. This can be done by giving the “ps” command in the prompt.

$  ps
PID      TTY   TIME  CMD
4882522  pts/7  0:00 ps
4984988  pts/7  0:00 -sh

4. Identify the PID of the script which is is shifted to background. In our case “script1″ This can be done by ps command piped with grep as below.

$ ps -ef | grep script1.ksh
user1 4399240 4984988   0 08:57:49  pts/7  0:00 grep script1.ksh
user1 5029960 4829226   0 07:57:23      -  0:00 /usr/lpp/ars/bin/script1.ksh

5. Now with all the PID’s collected, use “nohup” command

$ nohup -p 4984988
$ nohup -p 5029960

This will make the script or process not to be terminated even if the telnet session is closed.

NB: The telnet session process 4984988, will be running at the background unless it is killed.

Courtesy: Santhosh Fabian

Unique visitors to post: 351