@tom-righele
Forum Replies Created
-
AuthorReplies
-
BUMPin’ this!
Anyone have any insight?
-Tom
Thank you Levy! This does help very much. Appreciate you taking the time on this!
Sorry Charlie, I should have been a bit more clear with my initial post.
The main issue I was having is when I used a scheduled UPoC to exec a cmd script that changed sites and performed the statistics tcl.
Each site needs to be set prior to running the statistics tcl to get that site’s stats. When it was time for the UPoC to run, it would ignore the “setsite” command and stay on the site that I am running the scheduled UPoC on.
However, if I change the site on the tps on the schedules UPoC using the below code, I can then simply exec a cmd script that performs the statistics tcl.
If you are interested, I can post the code here later. Let me know!
-Tom 8)
Hello all-
Wanted to update everyone as I was able to fix my issue!
I used the the below statement to change my site at the parent process:
Code:
if ![catch {netcfgLoad} err] {
NCFG:ChangeSite $siteDir
netcfgLoad
}I cycled through all the sites that I wanted to run my scripts on and changed the site before I executed my script.
Thank you everyone for your input!
Tom
Thank you all for your input. I am going to try some of these things later on tonight.
First, let me preface this with what we are running. We are on 6.1.2.3 and running in Windows OS.
The goal of this script is to output statistics to folder in a csv format so another thread can grab these files and store them to a sql db.
In the usercmds folder under the root directory, I have two scripts. Transactioncountcycle.cmd and trans_to_file.tcl. The trans_to_file uses msiAttach to gather statistics for the current site you are on, and outputs to a csv. The Transactioncountcycle.cmd sets each site and runs the trans_to_file for each one. I had to do this because you cannot change sites when you use msiAttach in a single proc.
I have this UPoC that executes the Transactioncountcycle.cmd in our maintenance site, and whenever it’s run, it ignores the setsite command and runs the trans_to_file only fo the maintenance site. I am guessing that since the site the UPoC is on is considered the “parent environment” and it will not take change the sites based off child proc.
I am fortunate to also be attending Cloverleaf Intermediate class (with James D.) and the he advised that I could run a scheduled task to simply run the Transactioncountcycle.cmd. This should work and it is something I will try tonight. Props to James!
However, I would like to keep this all within Cloverleaf if possible, so if anyone has any other ideas, please let me know.
P.S. We are ALSO migrating to Linux, so we have a TEST environment under that OS. I was able to get this to work there using a sh that basically does the same thing as the Transactioncountcycle.cmd
Thank you all for your responses!
I’ve been playing around with these and I’m still having some trouble. I apologize, I’m not very familiar with SQLite. 😳
I’ve copied a smatdb to a test folder and ran the smatdb2nl against the file, but I am not seeing anything. Should I be seeing some type of output after I run the file?
Thanks again and apologize for the questions!
Thank you Mark! I’m unfortunately working with encrypted smatdb files. Anyway to get around this easily?
-Tom
Hey all! Your comments are all appreciated by the Valley Team!
Thank you all for the information!
-Tom 8)
Does anyone have any feed back at all?
Thanks Rob- I looked up a few examples of TCL’s that use the tclcurl method and these calls used a cleanup function:
$curlHandle cleanup
This seems to do the trick! Hopefully this helps someone in the future.
Thanks,
Tom
Thank you so much! This worked perfectly =)
THANK YOU!!!! This fixed the issue, I sincerely appreciate your help Jeff! And this is good to know as we migrate other items from Linux.
-Tom
Thank you, but I am still having issues
Thank you all!! That seemed to do something, but this seems to have caused another problem I was not seeing before. It seems more like an issue with xmlgen.tcl. I am getting this error now:
Error: invalid command name “setTagformat”This is a command from the xmlgen. The code is below. Is there something Linux does not read correctly in this TCL?
Code:########################################################################
#
# xmlgen — generate XML by writing Tcl code
#
# (C) 2002 Harald Kirsch
#
# $Revision: 1.9 $, $Date: 2002/09/21 14:55:55 $
########################################################################
package provide xmlgen [lindex {Revision: 1.0 } 1]namespace eval ::xmlgen {
namespace export buffer channel declaretag esc put doTag
setTagformat
## will be elongated and trimmed back by (recursive) calls to doTag,
## i.e. by tag-procs. However, it is only used by makeTagAndBody.
variable indent “”## a regular expression used by makeTagAndBody to identify
## tag-arguments which are attribute-value pairs as well as to
## dissect them into these two parts. The attribute name must match
## the definition of ‘Name’ found in the XML spec:
## http://www.w3c.org/TR/2000/REC-xml-20001006#NT-Name
## ‘CombiningChar’ and ‘Extender’ are not yet considered.
variable attrre {^ *([A-Za-z_:][a-zA-Z0-9_.:-]*)=(.*)}## A pattern used with [string match] to check if the first body
## argument of a markup proc is a control character which describes
## how to handle the body.
set controlchars {[-!+.]}## The following array specifies how to format the output. For every
## control character listed above it tells us what to put in front
## of the open and close tags — typically a newline and some
## indentation. Note that the respective strings are ran through
## [subst] in order to expand references to $indent. Consequently
## you must be careful to put other Tcl special characters into the
## string.
array set tagformat {
-o {n$indent$tag} -c {$tag}
+o {n$indent$tag} +c {n$indent$tag}
!o {n$indent$tag} !c {n$indent$tag}
.o {$tag} .c {$tag}
}## Output normally goes just to stdout, but proc buffer may be used
## to generate a context in which output is appended to this
## variable.
## NOTE: this is not thread-save if two threads operate in the same
## interpreter.
variable buffer “”## We want to replace the original puts by our own implementations
## depending on context. However, we need of course the original
## somewhere, so we keep it as tclputs. Then, initially, we make the
## “normal” ::puts an alias for the saved proc.## EAS: This is very confusing and didn’t work on my system
## Left the original TCL puts alone and called our proc “putx” instead
# rename ::puts ::xmlgen::tclputs
# HK: no put, use just [put] for redirectable and channelable output.
#interp alias {} ::putx {} ::xmlgen::putx## The main output-generating function is [put]. In contrast to puts
## it takes several arguments which are simply [join]ed and no
## newline is automatically appended. When called in the context of
## [buffer] or [channel], the output is redirected either to a
## variable or another output channel than stdout respectively. The
## default is output to stdout.
interp alias {} ::xmlgen::put {} ::xmlgen::putStream stdout
}proc ::xmlgen::putx-no-longer-needed-use-just-put {args} {
set i 0
if { “-nonewline” == [lindex $args $i] } {
set nl “”
incr i
} else {
set nl n
}## If there are still two args, the first is supposed to be an
## explicit output channel and we leave it to the original puts to
## handle that.
if { [llength $args]-$i != 1 } {
eval puts $args
return
}
variable buffer
append buffer [lindex $args $i] $nlreturn
}
## A version of [put] used when collecting output in a buffer.
proc ::xmlgen::putBuf {args} {
variable buffer
append buffer [join $args]
return
}## A version of [put] used when printing to a channel.
proc ::xmlgen::putStream {channel args} {
puts -nonewline $channel [join $args]
return
}## Arranges for further output to be appended to variable bufname
## instead of being sent automatically to stdout
proc ::xmlgen::buffer {bufname body} {
## save the current buffer locally
variable buffer
set keptBuffer $buffer
set buffer {}## stack the current redirection
set keptPut [interp alias {} ::xmlgen::put]## redirect [put]
## FIXME: Is it really necessary to work with the namespace-variable
## buffer to collect the output or could we do something like
## interp …. {} xmlgen::putBuf $bufname
## Probably not, because then $bufname could not refer to a local
## variable of the calling function.
interp alias {} ::xmlgen::put {} ::xmlgen::putBuf## run the body safely
set err [catch {uplevel 1 $body}]
## Restore [put]
eval interp alias {{}} ::xmlgen::put {{}} $keptPut## copy the collected buffer to the requested var and restore the
## previous buffer
upvar $bufname b
set b $buffer
set buffer $keptBuffer
if {$err} {
return -code error -errorinfo $::errorInfo
}
return
}proc ::xmlgen::channel {chan body} {
## stack the current redirection
set keptPut [interp alias {} ::xmlgen::put]## redirect [put]
interp alias {} ::xmlgen::put {} ::xmlgen::putStream $chan## run the body safely
set err [catch {uplevel 1 $body}]
## Restore [put]
eval interp alias {{}} ::xmlgen::put {{}} $keptPutif {$err} {
return -code error -errorinfo $::errorInfo
}
return
}## See manual page for description of this function.
proc ::xmlgen::makeTagAndBody {tagname l {specialAttributes {}} } {
variable attrre
variable indent
variable controlchars## If specialAttributes is set, we put those attributes into the
## array instead of assembling them into the tag.
if {”$specialAttributes”==””} {
array set sAttr {}
} else {
upvar $specialAttributes sAttr
}
## Collect arguments as long as they look like attribute-value
## pairs, i.e. as long as they match $attrre.
## As a convenience, an argument which is the empty string is simply
## ignored. This allows optional, auto-generated attributes to be
## empty and skipped like in
## if {…} {set align “”} else {set align “align=center”}
## p $align – {Some text, sometimes centered}
## If $align==””, it will not stop attribute processing.
##
set opentag “<$tagname"
set L [llength $l]
for {set i 0} {$i attr value]} break
if {[info exists sAttr($attr)] || “”==”$tagname”} {
set sAttr($attr) $value
} else {
append opentag ” $attr=”[esc $value]””
}
}
## If there is at least one element left in $l, the first element of
## $l is already stored in arg. It could be the argument controlling
## how to handle the body.
set haveControl 0; # see safety belt below
set control .
if {$i<$L} {
if {[string match $controlchars $arg]} {
set control $arg
incr i
set haveControl 1
} elseif {[string length $arg]==1} {
append emsg
" starting the body with a single character is not allowed "
"in order to guard against bugs"
return -code error $emsg
}
}
## If there are elements left in $l they are joined into the
## body. Otherwise the body is empty and opentag and closetag need
## special handling.
if {$i”
set closetag “”## Do some indenting.
set opentag [formatTag ${control}o $indent $opentag]
set closetag [formatTag ${control}c $indent $closetag]
} else {
## Leave a space in front of “/>” for being able to use XHTML
## with most HTML-browsers
set body {}
append opentag ” />”
set closetag “”
}
## Put on the safety belt. If we did not have a control character
## and the body starts with a blank line, the author most probably
## just forgot the control character.
if {!$haveControl && [regexp “^[t ]*n” $body]} {
append msg
“body starts with newline but no control ”
“character was given:”
set b [split $body n]
if {[llength $b]>3} {
append msg [join [lrange $b 0 3] n] ” …”
} else {
append msg $body
}
return -code error $msg
}
return [list $opentag $control $body $closetag]
}
########################################################################
## With the help of variable tagformat we put some indentation in
## front of a tag to make the output look nicer.
proc ::xmlgen::formatTag {which indent tag} {
variable tagformat
return [subst $tagformat($which)]
}
########################################################################
##
## Sets an element of variable tagformat in a controlled way, i.e. we
## test if the array index ‘which’ makes sense.
##
proc ::xmlgen::setTagformat {which format} {
variable tagformat
variable controlchars
if {![regexp “$controlchars[oc]” $which]} {
return -code error
“the string `$which’ is not a valid target to format”
}
set tagformat($which) $format
}
########################################################################
## Evaluate, substitute and print or just return the body
## enclosed in the given opentag and closetag.
proc ::xmlgen::runbody {opentag control body closetag} {switch -exact — $control {
“!” {
variable indent
set ind $indent
append indent { }
uplevel 1 [list ::xmlgen::put $opentag]
uplevel 1 $body
uplevel 1 [list ::xmlgen::put $closetag]
set indent $ind
}
“+” {
set body [string trim $body “n t”]
uplevel 1 [list ::xmlgen::put $opentag]
uplevel 1 “::xmlgen::put [subst {$body}]”
uplevel 1 [list ::xmlgen::put $closetag]
}
“-” {
set body [string trim $body “n t”]
uplevel 1 [list ::xmlgen::put $opentag]
uplevel 1 [list ::xmlgen::put $body]
uplevel 1 [list ::xmlgen::put $closetag]
}
“.” {
return “$opentag$body$closetag”
}
default {
return -code error “unknown control string `$control'”
}
}
return
}
########################################################################
## Generic function to handle a tag-proc and its arguments.
proc ::xmlgen::doTag {tagname args} {
variable tagAndBodyProc
foreach {opentag control body closetag}
[makeTagAndBody $tagname $args] break
set result [uplevel 1 [list ::xmlgen::runbody $opentag
$control $body $closetag]]return $result
}## Makes a tagname into a tag-proc by making it into an alias for
## doTag.
proc ::xmlgen::declaretag {funcname {tagname {}}} {
if {”$tagname”==””} {
set tagname $funcname
}
set ns [string trimright [uplevel 1 “namespace current”] :]
interp alias {} [set ns]::$funcname {} ::xmlgen::doTag $tagname
return
}## Convert text so that it is safe to use it as an attribute value
## surrouned by double quotes as well as character data. See the
## definition of AttValue and CharData:
## http://www.w3c.org/TR/2000/REC-xml-20001006#NT-AttValue
## http://www.w3c.org/TR/2000/REC-xml-20001006#NT-CharData
proc ::xmlgen::esc {args} {
regsub -all “&” [eval concat $args] “\&” args
regsub -all “” $args “\>” args
regsub -all “”” $args “\"” args
regsub -all “]” $args “\]” args
return $args
}########################################################################
Any help is much appreciated!
-
AuthorReplies
