nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

editioncount.ipl

bpg

when using the above .ipl, where is the output ported to? is it possible to pipe it to a text file?

regards,

brendan gleeson

Find more posts tagged with

Comments

Migrateduser

What is this file? Where does it live, etc.? What version / OS are you using? This sounds like a custom script, not OOTB.

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

Dwayne

I've never heard of editioncount.ipl. Perhaps it's custom code for your installation?

In general, however, you can usually redirect STDOUT by doing something like

editioncount.ipl > /path/to/output/file

And if you want STDERR in the same file:

editioncount.ipl > /path/to/output/file 2>&1

--

Current project: TS 5.5.2/6.1 W2K

bpg

apologies, not enough info given.

were on TS 5.5.2 SP 6 on W2K SP4 platform

i found this ipl on devnet and it looked like an easy way to calculate the number of editions, as we have many branches to maintain. but i dont know where the output is dumped or how to dump it somehere else. heres teh code from the script:

#!iwperl -w
#=====================================================================
# Traverse a directory path finding the number of editions on each branch
# The number of directories processed is displayed periodically,
# primarilly just to provide a sense of the script's status.
# All output is sent to STDERR to prevent buffering.
#=====================================================================
use TeamSite::Config;
use Getopt: Smiley Frustrated

td;
#---------------------------------------------------------------------
my $iwhome = TeamSite::Config::iwgethome();
my $iwmount = TeamSite::Config::iwgetmount();
my $DEBUG = $ENV{EDCOUNT_DEBUG} || 0;
my %opts;
#---------------------------------------------------------------------
usage("bad arg:\nUsage:") if (!getopts("hvb:", \%opts));
die "$0 v. 2003-05-31" if ($opts{v});
usage("Usage:") if ($opts{h});
sub usage{
die("$_[0] $0 -h | -v | [-b branchpath]\n",
"Additional output can be enabled by setting the environment\n",
"variable EDCOUNT_DEBUG to a non-zero value.\n");
}
#---------------------------------------------------------------------
my $archive = $opts{b} || "/default/main";
warn "[" . scalar(localtime()). "]: Beginning processing of $archive ...\n";
my $checked = 0;
process_dir($archive);
warn "[" . scalar(localtime()). "]: Finished checking $checked directories.\n";

#=====================================================================
# process_dir($dir)
# Traverse through the TeamSite EDITION area, on a given branch
# and sub-branches, checking the number of editions in each
# edition directory processed.
#
# Warnings for large numbers of editions is indicated by leading
# asterisks in the output:
# "*" for directories that contain over 500 editions.
# "**" for directories that contain over 1000 editions.
# Optionally, if DEBUG is non-zero, display the number of editions
# for directories containing fewer than 500 entries too.
#=====================================================================
sub process_dir{
my $dir = shift;
warn "Checked $checked directories\n" if ($checked && $checked % 50 == 0);
$checked++;
my @subdirs;
if (opendir(DIR, "$iwmount$dir")){
my @entries = readdir(DIR);
closedir(DIR);
foreach my $e (@entries){
next if ($e =~ /^\./);
# only traverse down editions areas
next if ($e eq "STAGING" || $e eq "WORKAREA");
if ($e eq "EDITION"){
warn "... checking $dir ...\n" if (!$DEBUG);
if (opendir(DIR, "$iwmount$dir/$e")){
my @EdS = readdir(DIR);
closedir(DIR);
my $count = scalar(@eds) - 2;
warn sprintf("**%5d editions in: $dir\n", $count)
if ($count >= 1000);
warn sprintf("* %5d editions in: $dir\n", $count)
if ($count >= 500 && $count < 1000);
warn sprintf(" %5d editions in: $dir\n", $count)
if ($count < 500 && $DEBUG);
}
}
else {
push(@subdirs, "$dir/$e") if (-d "$iwmount$dir/$e");
}
}
}
foreach my $e (@subdirs){
process_dir($e);
}
}

regards,

brendan

Migrateduser

What output are you looking for? It has warn statements, but those are written to STDOUT when using the -w flag, for instance.

Are you looking to have this script log something (because it doesn't do that currently)?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

bpg

forgive me, cos i aint a coder im a sys admin.

i was expecting the script to give me an output of the number of editions that currently reside in a backing store, so that i could easliy target areas for house-keeping. also, does this script just run on the default backing store or is it poss to run it against a second?

many thanks,

brendan

Migrateduser

No problem.

If you call the script using the -w flag, then you will see output and the script only looks in the default backing store. This is configurable, however, if you were to change the value of $iwmount.

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

Adam Stoller

This looks like a script I may have written - as such, it was meant to be run from the command line (not as a custom menu item, nor from a workflow).

I don't see where a '-w' flag comes into play (other than the one associated with iwperl) - it does have a '-b' flag for specifying the initial branch path to begin traversal, but the output is sent to STDERR (not STDOUT) and, as the comments indicate, if you set the environment variable EDCOUNT_DEBUG to a non-zero value, additional output will be displayed as well.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

TestReportWithGrouping.rptdesign

TestReportWithoutGrouping.rptdesign

Adam Stoller

I should also mention that, if this is the script I wrote, then the script was intendend for pre-5.5.2 systems - where the number of editions on a given branch tended to be a factor in terms of TS performance. 5.5.2 does not have that problem, but knowing how many editions are on a given branch might provide a clue as to where you might be able to reclaim some disk space - but that's about it.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

The -w flag I referred to was for the iwperl interpreter, itself. If I'm not mistaken, your script will write the warnings to STDOUT if the -w flag is present, no?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 5.5.2 SP2 on Win2K

Adam Stoller

No - the '-w' for iwperl is to spit out any diagnostic warnings about the code itself when perl tries to interpret the code - it has nothing to do with the code that actually gets run.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

bpg

ok, many thanks for your thoughts on this but is it possible for someone to tell me the exact command i need to run so that i can get a calculation of all existing editions? we have a large number of branches and i aim to keep the teamsite app as "trim" as possible, so am looking to keep on top of the number of editions.

i also dont understand what you mean by the output goes to STDERR. what does this mean?

many thanks in advance,

brendan

Adam Stoller

You're on Windows - right?
Open up a command prompt on the TS Server,

C:\> \path\to\editioncount.ipl 2>&1 > \path\to\logfile.txt

That should probably do it - once you run the script - look at the contents of \path\to\logfile.txt

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

bpg

hello again,

i ran this command and it created the log file but the file was empty. any ideas?

thanks,

brendan

correctFilter.JPG

Adam Stoller

Sorry - my syntax was wrong for the command line - Try this:

c:\> set EDCOUNT_DEBUG=1
c:\> \path\to\editioncount.ipl > \path\to\logfile.txt 2>&1

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

bpg

fantatstic, this is exactly what i needed. many thanks for your help and suggestions.

brendan