1. What is the Foxboro approved way to install java on a Solaris 2.5 system?
2. Any tricks in doing a windows install of java?
3. Are there any Solaris limitations in CALCView?
4. Are there any Windows limitations in CALCView?
5. How do I use Exceed (or remote workstations) with CALCView?
5. How do I create an ICC driver task dump?
1. What is the Foxboro approved way to install java on a Solaris 2.5 system?
Solaris 2.5 systems require Java 1.2.2 which is avalable from Sun (http://java.sun.com/j2se/downloads.html).
6.1 and 6.3 (not 6.5 and higher) systems also requires the installation of
4 Solaris patches which are also available from Sun:
103461-33 http://sunsolve.sun.com/pub-cgi/findPatch.pl?patchId=103461=33
103566-56 http://sunsolve.sun.com/pub-cgi/findPatch.pl?patchId=103566=56
103627-13 http://sunsolve.sun.com/pub-cgi/findPatch.pl?patchId=103627=13
103640-37 http://sunsolve.sun.com/pub-cgi/findPatch.pl?patchId=103640=37
To install the patches use the following steps:
- Enter single user mode
- Install above patches
- Reboot
2. Any tricks in doing a windows install of java?
No tricks. Just follow the instructions on Sun's web site. You can use the
latest version - JRE 1.4.1 as of this writing.
3. Are there any Solaris limitations in CALCView?
The only thing wrong with CALCView on a Solaris system
is a few of the dialogs get a blue border. We believe this is due to a bug
in Java 1.2.2 and are looking for a way around it. However, the program
is still completely functional.
4. Are there any Windows limitations in CALCView?
The icc driver task fail during an upload or a download for some unknown reason
(spinit problem). We are looking into a fix or a workaround. You
can manually dump blocks with the icc driver task an open them in CALCView
for debugging.
** FIXED: Just make sure CALCView is on the same partition as the Foxboro system (usually D:)
5. How do I use Exceed (or remote workstations) with CALCView?
To run CALCView remotely with Exceed, use the following scripts:
1) in /usr/fox/config (called CALCView):
dmcmd script wp_applic /Path to second script/RunCV $DISPLAY
2) in CALCView directory or anywhere else (called RunCV):
#!/bin/sh if [ $# -eq 0 ] then DISPLAY=127.0.0.1:0.0 export DISPLAY else DISPLAY=$1 export DISPLAY fi cd /opt/todbaudais/CALCView/ java -jar CALCView.jar &
NOTE: Don't forget to do "chmod 777 RunCV" on the second script.
In exceed under the Screen Definitions setting, change "Default to Native" to "Native". If you don't, the title bars disappear. Be aware that Java programs running under exceed behave quite poorly. Screen updates are rather slow. However, CALCView runs just fine from remote Solaris workstations.
6. How do I create an ICC driver task dump?
I use one of two shell script depending on what I am doing. They work pretty
much the same except their output is different.
The first script, DumpAllICC, dumps each of the CPs and Gateways, in turn,
to the standard output. This script would typically be used to create the
input for the ICCCompare program.
#!/bin/sh
#This script dumps the contents of all the attached modules
#to the standard output
for cp in `cat /etc/cplns/`
do
/opt/fox/ciocfg/api/iccdrvr.tsk << EOF
OPEN $cp READ iccdumper
GET *:* ALL
CLOSE
EXIT
EOF
done
You would use the program like this:
DumpAllICC > MyICCDump
The second script, DumpAllICCInd, dumps each CP or gateway to a separate file
in a directory called "dumps" with the file name being its letterbug.
This script would typically be used to create the input for the ICCReporter
program since it places the file name (i.e. the Letterbug if you use this
script) in the first column of the output.
#!/bin/sh
#This script dumps the contents of all the attached modules
#to a directory
mkdir dumps
for cp in `cat /etc/cplns/`
do
/opt/fox/ciocfg/api/iccdrvr.tsk > dumps/$cp << EOF
OPEN $cp READ iccdumper
GET *:* ALL
CLOSE
EXIT
EOF
done
