|
|
|
|
|
|
| Author |
Message |
John Gemignani, Jr.
*nix forums beginner
Joined: 13 May 2005
Posts: 12
|
 Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: HP parody site
|
|
|
"JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message
news:1107333752.c310f17c2c4ceadb82f1ecec60905201@teranews...
It's also proof that PH doesn't see a future in VMS ... um ... SMV. |
|
| Back to top |
|
 |
John Smith
*nix forums Guru
Joined: 15 Oct 2003
Posts: 561
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: HP parody site
|
|
|
John Gemignani, Jr. wrote:
| Quote: | "JF Mezei" <jfmezei.spamnot@teksavvy.com> wrote in message
news:1107333752.c310f17c2c4ceadb82f1ecec60905201@teranews...
Z wrote:
http://www.everythingispossible.com/
As expected, no mention of VMS. Proof that HP doesn't see a future
in VMS.
:-)
It's also proof that PH doesn't see a future in VMS ... um ... SMV.
|
Actually not. It's a parody so only the author of the site is not mentioning
VMS.....wait a minute...that's *exactly* what HP does.
From that I'd have to guess that the author of the site is carly(tm) writing
under a pseudonym. |
|
| Back to top |
|
|
David B Sneddon - bigpond
*nix forums addict
Joined: 21 Jul 2005
Posts: 68
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: %DCL-W-OKTAB again...
|
|
|
Larry Kilgallen was overheard to say:
| Quote: | In article <42006FAD.2070207@bigpond.com>, David B Sneddon - bigpond <dbsneddon@bigpond.com> writes:
Larry Kilgallen mentioned in passing:
As I said, it _probably_ means "the program you ran just returned a
random binary number", but it is hard to say until you do the work
to find out what program it is.
From the source listings... the value for the OKTAB message
is 261141 which results in the following
tardis_FTA77> say f$message(261441)
%CLI-S-OKTAB, command tables are already in latest format
Since you are getting %DCL-W-OKTAB rather that %CLI-S-OKTAB
would further support Larry's claim.
Actually, although I stand by my claim, I am not sure _that_ difference
supports it. I recall in the dark past that %CLI messages get changed
to %DCL messages in certain circumstances.
|
The real message is a success whereas the suspect one is a
warning. My other reply shows the difference between
f$message(261440) and exit 261440 which does change the
facility from CLI to DCL.
Regards,
Dave.
--
David B Sneddon (dbs) VMS Systems Programmer dbsneddon@bigpond.com
Sneddo's quick guide ... http://www.users.bigpond.com/dbsneddon/
DBS freeware http://www.users.bigpond.com/dbsneddon/software.htm |
|
| Back to top |
|
|
JF Mezei
*nix forums Guru
Joined: 21 Jul 2005
Posts: 2556
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: vaxcluster vms v5.5-2 and v7.3
|
|
|
Charlie Hammond wrote:
| Quote: | Here is an example the will illustrate how this implication may not work:
John loves Mary and Mary loves Bill.
Does this imply that John loves Bill?
|
It does imply that Bill will get John's diseases though (due to MSCP
ensuring that they are transfered between nodes in this 3 node cluster).
But this still doesn't explain what has changed in the SCS protocol to
cause 5.5-2 not to interact with 7.2.
Someone mentioned the volume shadowing code. Fine. But if you don't use
volume shadowing, would changes to it affect your ability to cluster ? |
|
| Back to top |
|
|
Dave Froble
*nix forums Guru
Joined: 21 Jul 2005
Posts: 1172
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: vaxcluster vms v5.5-2 and v7.3
|
|
|
JF Mezei wrote:
| Quote: | Charlie Hammond wrote:
Here is an example the will illustrate how this implication may not work:
John loves Mary and Mary loves Bill.
Does this imply that John loves Bill?
It does imply that Bill will get John's diseases though (due to MSCP
ensuring that they are transfered between nodes in this 3 node cluster).
|
Not so, it doesn't imply that Mary loves John.
| Quote: | But this still doesn't explain what has changed in the SCS protocol to
cause 5.5-2 not to interact with 7.2.
|
If it's a basic incompatibility, then no clustering can happen. IF the basics
are the same, then you may be able to form a cluster, but the devil is in the
details of what will work, and what will not work. I don't know the answer to that.
| Quote: | Someone mentioned the volume shadowing code. Fine. But if you don't use
volume shadowing, would changes to it affect your ability to cluster ?
|
|
|
| Back to top |
|
|
Richard Maher
*nix forums Guru Wannabe
Joined: 15 Jun 2005
Posts: 275
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: OT: Battersea Power Station
|
|
|
Hi,
I don't think that anyone else has mentioned it so for the record, Battersea
Park power station reached the pinnacle of photo opportunities when it
starred in MacGyver as a back-drop to the war in Yugoslavia. Disbelief! (No,
I'm not a MacGyver, fan we just get a lot of wet weekends here and they were
re-running it a couple of years ago)
I believe it is currently being used as a lightshow backdrop fot the London
2012 Olympic bid logo. (Now there's a real joke. But I digress.)
Regards Richard Maher
PS. Why has one of the chimneys been given some sort of navy blue
flame/crown at its base?
"Paddy O'Brien" <paddy.o'brien@transgrid.com.au> wrote in message
news:41FDF2F9.2010605@transgrid.com.au...
| Quote: |
Dr. Dweeb wrote:
Hi,
Sometime ago someone responding on this newsgroup had a pointer to their
photography site - name and site lost in the mists. Anyway, there was a
great picture (b/w) of the Battersea Power Station.
If you spot this you might leave me the address. I am perhaps
interested in
acquiring a print (a large one).
Thanks
Dr. Dweeb
I've just got back from 5 weeks leave. Sortta confused between US and
UK -- is 01/02 second of Jan or first of Feb (which hasn't quite
happened yet :-)
Battersea Power Station was featured in one of the Cristopher Reeve
Superman films -- the one where he fought his alter ego. Some excellent
shots of the site (between the fights).
Is the station still going? I worked for CEGB and left in 1982 when
Battersea was scheduled to be closed within 5 years. The A station was
already shut down.
Regards, Paddy
***********************************************************************
"This electronic message and any attachments may contain privileged
and confidential information intended only for the use of the
addressees named above. If you are not the intended recipient of
this email, please delete the message and any attachment and advise
the sender. You are hereby notified that any use, dissemination,
distribution, reproduction of this email is prohibited.
If you have received the email in error, please notify TransGrid
immediately. Any views expressed in this email are those of the
individual sender except where the sender expressly and with
authority states them to be the views of TransGrid. TransGrid uses
virus-scanning software but excludes any liability for viruses
contained in any attachment.
Please note the email address for TransGrid personnel is now
firstname.lastname@transgrid.com.au"
***********************************************************************
|
|
|
| Back to top |
|
|
Ryan Moore
*nix forums beginner
Joined: 13 May 2005
Posts: 13
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: vaxcluster vms v5.5-2 and v7.3
|
|
|
I also remember in the V6 timeframe that there were some changes to how
MOUNT worked as well.
I see from a developer's perspecitve since that's what I do for a living.
I'm going to guess there were lots of little changes to how clustering
worked over the years.
Here's a hypothetical situation that may be true:
Your requirement in 6.2 is that it clusters with 5.5-2. So you put in
code to handle that in 6.2.
Later you're developing 7.2 and you want to change protocols for new
functionality. But the 5.5 support code is in the way. So you get rid of
it or make changes such that it doesn't work any more. Or you don't
update the compatibility code since it would take too long. But that's
okay because they aren't required to be compatible anymore.
I'm sure clustering hasn't been static. The 64-bit and Galaxy changes
alone could require changing some cluster protocols. Software engineers
program to meet the requirements. If there is no requirement to cluster
8.2 and 5.5-2 then they aren't going to be thinking about that
compatibility when they make changes. And lots of little things could
break.
On Wed, 2 Feb 2005, JF Mezei wrote:
| Quote: | Charlie Hammond wrote:
Here is an example the will illustrate how this implication may not work:
John loves Mary and Mary loves Bill.
Does this imply that John loves Bill?
It does imply that Bill will get John's diseases though (due to MSCP
ensuring that they are transfered between nodes in this 3 node cluster).
But this still doesn't explain what has changed in the SCS protocol to
cause 5.5-2 not to interact with 7.2.
Someone mentioned the volume shadowing code. Fine. But if you don't use
volume shadowing, would changes to it affect your ability to cluster ?
|
|
|
| Back to top |
|
|
Charlie Hammond
*nix forums addict
Joined: 13 May 2005
Posts: 55
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: vaxcluster vms v5.5-2 and v7.3
|
|
|
In article <1107368501.2cf27fdad857b96f52402ddbbccb3a77@teranews>,
JF Mezei <jfmezei.spamnot@teksavvy.com> writes:
| Quote: | But this still doesn't explain what has changed in the SCS protocol to
cause 5.5-2 not to interact with 7.2.
Someone mentioned the volume shadowing code. Fine. But if you don't use
volume shadowing, would changes to it affect your ability to cluster ?
|
As has been said repeatdly, we have not tested this and
do not know whether it will or will not work.
--
Charlie Hammond -- Hewlett-Packard Company -- Ft Lauderdale FL USA
(hammond@not@peek.ssr.hp.com -- remove "@not" when replying)
All opinions expressed are my own and not necessarily my employer's. |
|
| Back to top |
|
|
Rich Alderson
*nix forums beginner
Joined: 13 May 2005
Posts: 39
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: Official Logo
|
|
|
Alan Frisbie <Usenet02_REMOVE@Flying-Disk.com> writes:
| Quote: | The Cheshire Cat was a good one.
|
Of course, Chester was *not* the Cheshire Cat. There was a specific difference
between the Disney character that inspired Chester and the VAX mascot himself--
DECUS had to negotiate with the Disney folks to be able to use Chester at all,
and the difference was required by the licensing agreement.
Then the 36-bit folks misappropriated Chester for the 20th and 25th anniversary
T-shirts ("I ain't afraid of no VAX!" and "I ain't afraid to take RISCs!").
Poor Betsy...
So wasn't Chester a DECUS thing rather than a DEC logo?
--
Rich Alderson | /"\ ASCII ribbon |
news@alderson.users.panix.com | \ / campaign against |
"You get what anybody gets. You get a lifetime." | x HTML mail and |
--Death, of the Endless | / \ postings | |
|
| Back to top |
|
|
Rich Alderson
*nix forums beginner
Joined: 13 May 2005
Posts: 39
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: Official Logo
|
|
|
"Kenneth Farmer" <kfarmer@NOSPAM.spyderbyte.com> writes:
| Quote: | "DeanW" <dean.woodward@gmail.com> wrote in message
news:3f119ada05020123307d1ed8d5@mail.gmail.com...
Somehow, Ivanhoe's uprooted Oak seems appropriate
OK I never read Ivanhoe. What does this mean?
|
At a tourney at which he was riding in disguise, his shield bore an uprooted
oak tree and declared him disinherited.
--
Rich Alderson | /"\ ASCII ribbon |
news@alderson.users.panix.com | \ / campaign against |
"You get what anybody gets. You get a lifetime." | x HTML mail and |
--Death, of the Endless | / \ postings | |
|
| Back to top |
|
|
Christoph Gartmann
*nix forums Guru Wannabe
Joined: 26 May 2005
Posts: 146
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: %DCL-W-OKTAB again...
|
|
|
In article <42010D0A.7040500@bigpond.com>, David B Sneddon <dbsneddon@bigpond.com> writes:
| Quote: | The real message is a success whereas the suspect one is a
warning. My other reply shows the difference between
f$message(261440) and exit 261440 which does change the
facility from CLI to DCL.
|
Now I found at least a way to fix the problem or the cause why it happened.
But I still don't understand what this message actually means. I mean, the
webserver doesn't do any attempts to modify the DCL tables. It uses
CLI$-routines to parse a configuration file and for some reason gets this
success message and translates it into a warning. Somehow odd.
Regards,
Christoph Gartmann
--
Max-Planck-Institut fuer Phone : +49-761-5108-464 Fax: -452
Immunbiologie
Postfach 1169 Internet: gartmann@immunbio dot mpg dot de
D-79011 Freiburg, Germany
http://www.immunbio.mpg.de/home/menue.html |
|
| Back to top |
|
|
Chris Scheers
*nix forums beginner
Joined: 13 May 2005
Posts: 44
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: vaxcluster vms v5.5-2 and v7.3
|
|
|
John Laird wrote:
| Quote: | On Tue, 01 Feb 2005 09:21:42 -0800, "Tom Linden" <tom@kednos.com> wrote:
On Tue, 01 Feb 2005 17:14:14 +0000, John Laird
nospam@laird-towers.org.uk> wrote:
It looks like 7.2 was about the point that 5.5-2 became too old, if not
before.
Well the reason I asked was because I had 6.2 clustered with 7.3, so it
seems
that if A ~ B & B ~C -> A ~C ?
If you're suggesting what I think you're suggesting, that 6.2 can play with
5.5-2 and 7.3, so why can't they play together, the answer almost certainly
lies in the necessary remedial kit for 6.2 to cluster with 7.2 and up. So
it's not quite the same 6.2 in both cases.
This doesn't preclude the possibility that it might *appear* to work, but I
would take the release notes at face value - rarely have VMS engineering
used a phrase like "will not work" when "unsupported" will do.
|
From what I understand, when a node tries to join a cluster, a protocol
is negotiated. If the other nodes can talk the same protocol, the node
is allowed to join.
Doing a quick check with SHOW CLUSTER, I see that VAX 5.5-2 is protocol
23, Alpha 6.1 is protocol 24, and Alpha 7.1 is protocol 26.
So, if 7.2 dropped support for protocol 23 (This is pure supposition on
my part), it would become impossible for 7.2 to cluster with a 5.5-2
node, even though it can cluster with a node that can also cluster with
5.5-2.
This is kind of like shareable image version numbers. They protect you
from running combinations which may cause problems, but they also
prevent you from running combinations which would have worked because
you don't use the problematic features.
--
-----------------------------------------------------------------------
Chris Scheers, Applied Synergy, Inc.
Voice: 817-237-3360 Internet: chris@applied-synergy.com
Fax: 817-237-3074 |
|
| Back to top |
|
|
JF Mezei
*nix forums Guru
Joined: 21 Jul 2005
Posts: 2556
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: vaxcluster vms v5.5-2 and v7.3
|
|
|
Charlie Hammond wrote:
| Quote: | As has been said repeatdly, we have not tested this and
do not know whether it will or will not work.
|
Hey, we know it hasn't been tested. We know it isn't supported. But that
still doesn't prevent one from wanting to know about the evolution of
the clustering protocol over time which made 5.5-2 incompatible with
newer releases.
Consider that for the first time in VMS' history, we are contemplating
the "maturing" of one version of VMS (VAX) possibly at 8.2, possibly at
7.3. This means that the gap betwene VAX and Alpha will grow far more
now than in the past.
The question now becomes: Should engineers be tasked to design new
clustering software to be more flexible and versatile, allowing new
functionality while preserving connectivity with older (and hopefully
other systems ?)
Or will HP just kill VMS clustering and have customer get Veritas on VMS ? |
|
| Back to top |
|
|
Keith Cayemberg
*nix forums addict
Joined: 26 May 2005
Posts: 80
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: How do I use terminal emulator with escape sequences?
|
|
|
john_20_28_2000@yahoo.com wrote:
| Quote: | In Unix, I can enter:
echo "\033P\$smyterminalemulatorfile.psl \033\\"
In OpenVMS I have tried many variations with sys$output, but it just
prints to the screen and nothing happens on the client.
Please help me. Thank you.
|
I call the following DCL Procedure in my login.com to define terminal
codes which can be used in my own set of utilities or called at the DCL
prompt. I found the control codes in the VTxxx Manuals that come with
the DEC video Terminals. You will find these manuals online at...
http://vt100.net/
When embedding these definitions in your own procedures, remember to
make the symbol definitions local to the procedure by replacing
the "==" with "="
----------------------------cut-here-------------------------------------
CREATE DEFINE_TERMINAL_CODES.COM
$!***The following are VTxxx screen formatting commands***
$! They are intended to be used with WRITE SYS$OUTPUT
$! EXAMPLE:
$! SAY :== write sys$output
$! SAY ES,HOME,DW,"Hi There"
$!
$!C0 Control Characters (ASCII)
$ SOH_VT[0,8]==1 !set terminal SOH code
$ STX_VT[0,8]==2 !set terminal STX code
$ ETX_VT[0,8]==3 !set terminal ETX code
$ EOT_VT[0,8]==4 !set terminal EOT code
$ ENQ_VT[0,8]==5 !set terminal Enquire code (answerback)
$ ACK_VT[0,8]==6 !set terminal ACK code
$ BEL_VT[0,8]==7 !set terminal BEL code
$ BS_VT[0,8]==8 !set terminal Backspace code
$ HT_VT[0,8]==9 !set terminal Horizontal Tab code
$ LF_VT[0,8]==10 !set terminal Linefeed code
$ VT_VT[0,8]==11 !set terminal Vertical Tab code
$ FF_VT[0,8]==12 !set terminal Form Feed code
$ CR_VT[0,8]==13 !set terminal Carriage Return code
$ SO_VT[0,8]==14 !set terminal SO code
$ SI_VT[0,8]==15 !set terminal SI code
$ DLE_VT[0,8]==16 !set terminal DLE code
$ DC1_VT[0,8]==17 !set terminal DC1 code
$ DC2_VT[0,8]==18 !set terminal DC2 code
$ DC3_VT[0,8]==19 !set terminal DC3 code
$ DC4_VT[0,8]==20 !set terminal DC4 code
$ NAK_VT[0,8]==21 !set terminal NAK code
$ SYN_VT[0,8]==22 !set terminal SYN (Control V) code
$ ETB_VT[0,8]==23 !set terminal ETB code
$ CAN_VT[0,8]==24 !set terminal CAN code
$ EM_VT[0,8]==25 !set terminal EM code
$ SUB_VT[0,8]==26 !set terminal SUB code
$ ESC_VT[0,8]==27 !ESCAPE code for VT100 screen commands
$ FS_VT[0,8]==28 !set terminal FS code
$ GS_VT[0,8]==29 !set terminal GS code
$ RS_VT[0,8]==30 !set terminal RS code
$ US_VT[0,8]==31 !set terminal US code
$ SP_VT[0,8]==32 !set terminal SPace code
$ !combining a carriage return and linefeed
$ CRLF*VT:=="''CR_VT'''LF_VT'"
$ BELL*VT:== "''BEL_VT'" !rings bell
$!
$!C1 Control Characters (DEC)
$ IND*VT :== "''ESC_VT'D" !moves cursor down one line
$ NEL*VT :== "''ESC_VT'E" !moves to first position of next line
$ HTS*VT :== "''ESC_VT'H" !set horizontal tab at cursor position
$ RI*VT :== "''ESC_VT'M" !moves cursor up one line in same column
$ SS2*VT :== "''ESC_VT'N" !Temporary mapping of G2 Charset into GL
$ SS3*VT :== "''ESC_VT'O" !Temporary mapping of G3 Charset into GL
$ DCS*VT :== "''ESC_VT'P" !introduces a Device Control String
$ CSI*VT :== "''ESC_VT'[" !introduces a Control Sequence
$ CST*VT :== "''ESC_VT'\" !Control String Terminator
$ OSC*VT :== "''ESC_VT']" !introduces an Operating System Command
$ PM*VT :== "''ESC_VT'^" !introduces a Privacy Message string
$ APC*VT :== "''ESC_VT'_" !introduces Appl. Program Control string
$!
$!cursor movement control characters
$ !erase screen from cursor to bottom right corner
$ EStoEND*VT :== "''CSI'0J"
$ EStoHERE*VT :== "''CSI'1J" !erase screen from home to cursor
$ ES*VT:== "''CSI'2J" !erase entire screen
$ ESlinetoend*VT :== "''CSI'0K" !erase from cursor to end of line
$ ESlinetohere*VT :== "''CSI'1K" !erase begin of line to cursor
$ ESline*VT :== "''CSI'2K" !erase current line
$ ONEUP*VT :== "''CSI'1A" !jump up one line
$ TOP*VT:== "''CSI'H" !moves cursor to top/left screen
$!
$!
$!text size control characters
$ DHT*VT:== "''ESC_VT'#3" !sets top half of double high chars
$ DHB*VT:== "''ESC_VT'#4" !sets bottom half of double high chars
$ SWSH*VT :== "''ESC_VT'#5" !sets single width single height chars
$ DW*SHVT:== "''ESC_VT'#6" !sets double wide single height chars
$!
$!text attribute control characters
$ BOLD*VT:== "''CSI'1m" !sets bold characters
$ UNDER*VT:== "''CSI'4m" !sets underlined characters
$ BLINK*VT:== "''CSI'5m" !sets blinking characters
$ INVERSE*VT:== "''CSI'7m" !sets inverse characters
$ REVERSE*VT:== "''CSI'7m" !sets inverse characters
$ NORM*VT:== "''CSI'0m" !sets all char attributes to normal
$ BOLDOFF*VT :== "''CSI'22m" !turns off bold attribute
$ UNDEROFF*VT :== "''CSI'24m" !turns off underline attribute
$ BLINKOFF*VT :== "''CSI'25m" !turns off blink attribute
$ INVERSEOFF*VT :== "''CSI'27m" !turns off inverse attribute
$!
$!screen attributes control characters
$ SMOOTH*VT:== "''CSI'?4h" !sets smooth scrolling
$ JUMP*VT:== "''CSI'?4l" !sets jump scrolling
$ LIGHT*VT:== "''CSI'?5h" !sets light background
$ DARK*VT:== "''CSI'?5l" !sets dark background
$ FLASH*VT:== "''CSI'?5h''CSI'?5l" !flashes light then dark
$ FLASHBACK*VT:== "''CSI'?5l''CSI'?5h" !flashes dark then light
$ CURSOR*VT:== "''CSI'?25h" !shows cursor
$ CURSOROFF*VT:== "''CSI'?25l" !hides cursor
$!
$!status line control characters
$ STATUSMAIN*VT:== "''CSI'0$}" !select main display (VT3xx only)
$ STATUSLINE*VT:== "''CSI'1$}" !select status line (VT3xx only)
$ STATUSOFF*VT:== "''CSI'0$~" !turn off status line(VT3xx only)
$ STATUSON*VT:== "''CSI'1$~" !turn on status line (VT3xx only)
$ STATUSHOST*VT:== "''CSI'2$~" !turn on host-writbl (VT3xx only)
$!
$!local printer control characters
$ PLOFF*VT:== "''CSI'?4i" !print local off
$ PLON*VT:== "''CSI'?5i" !print local on
$!
$!terminal reset control characters
$ STRESET*VT:== "''CSI'!p" !soft terminal reset (VT3xx only)
$ HTRESET*VT:== "''ESC_VT'c" !hard terminal reset (VT3xx only)
$!
$!***emulate a MSDOS CLS command***
$ !clear screen and home cursor
$ ER*ASEVT :== WRITE SYS$OUTPUT ES,TOP
$ !clear screen, home cursor and soft reset
$ SRES*ETVT :== WRITE SYS$OUTPUT STATUSOFF,STRESET
$ !clear screen, home cursor and hard reset
$ HRES*ETVT :== WRITE SYS$OUTPUT HTRESET
$!
$!***Regis Terminal Color Settings***
$!
$! VT340 Default Color Map
$! MAP Color Symbol R G B H L S
$! 0 Black D 0 0 0 0 0 0 Text Backgrnd
$! 1 Blue B 20 20 80 0 50 60
$! 2 Red R 80 13 13 120 46 72
$! 3 Green G 20 80 20 240 50 60
$! 4 Magenta M 80 20 80 60 50 60
$! 5 Cyan C 20 80 80 300 50 60
$! 6 Yellow Y 80 80 20 180 50 60
$! 7 Gray 50% W 53 53 53 0 53 0 Text Foregrnd
$!
$! 8 Gray 25% D 26 26 26 0 26 0 Reverse
$! 9 Blue* B 33 33 60 0 46 29
$! 10 Red* R 60 26 26 120 43 39
$! 11 Green* G 33 60 33 240 46 29
$! 12 Magenta* M 60 33 60 60 46 29
$! 13 Cyan* C 33 60 60 300 46 29
$! 14 Yellow* Y 60 60 33 180 46 29
$! 15 Gray 75% W 80 80 80 0 80 0 Highlight
$! * - These colors are less saturated than the colors 1 thru 6
$!
$!
$! Now M7 = foreground M0 = background
$!
$!set dark background
$ Write sys$output dark
$!
$! The folowing combinations have bad contrast and are not defined:
$!
$! y_g, g_y, c_w, w_c , b_d, d_b, m_b, y_w, w_y, y_r, r_y
$!
$!white combinations
$ !blue on white
$ b_w*COLOR == "''ESC_VT'PpS(M0(W),M7(B),M8(D),M15(D))''ESC_VT'\"
$ !red on white
$ r_w*COLOR == "''ESC_VT'PpS(M0(W),M7(R),M8(D),M15(D))''ESC_VT'\"
$ !green on white
$ g_w*COLOR == "''ESC_VT'PpS(M0(W),M7(G),M8(D),M15(D))''ESC_VT'\"
$ !magenta on white
$ m_w*COLOR == "''ESC_VT'PpS(M0(W),M7(M),M8(D),M15(D))''ESC_VT'\"
$ !dark on white
$ d_w*COLOR == "''ESC_VT'PpS(M0(W),M7(D),M8(D),M15(R))''ESC_VT'\"
$!
$ !white on blue
$ w_b*COLOR == "''ESC_VT'PpS(M0(B),M7(W),M8(W),M15(D))''ESC_VT'\"
$ !white on red
$ w_r*COLOR == "''ESC_VT'PpS(M0(R),M7(W),M8(W),M15(D))''ESC_VT'\"
$ !white on green
$ w_g*COLOR == "''ESC_VT'PpS(M0(G),M7(W),M8(D),M15(D))''ESC_VT'\"
$ !white on magenta
$ w_m*COLOR == "''ESC_VT'PpS(M0(M),M7(W),M8(D),M15(D))''ESC_VT'\"
$!
$!black (dark) combinations
$ !red on dark
$ r_d*COLOR == "''ESC_VT'PpS(M0(D),M7(R),M8(W),M15(W))''ESC_VT'\"
$ !green on dark
$ g_d*COLOR == "''ESC_VT'PpS(M0(D),M7(G),M8(W),M15(W))''ESC_VT'\"
$ !magenta on dark
$ m_d*COLOR == "''ESC_VT'PpS(M0(D),M7(M),M8(W),M15(W))''ESC_VT'\"
$ !cyan on dark
$ c_d*COLOR == "''ESC_VT'PpS(M0(D),M7(C),M8(W),M15(W))''ESC_VT'\"
$ !yellow on dark
$ y_d*COLOR == "''ESC_VT'PpS(M0(D),M7(Y),M8(W),M15(W))''ESC_VT'\"
$ !white on dark
$ w_d*COLOR == "''ESC_VT'PpS(M0(D),M7(W),M8(W),M15(R))''ESC_VT'\"
$!
$ !dark on red
$ d_r*COLOR == "''ESC_VT'PpS(M0(R),M7(D),M8(W),M15(W))''ESC_VT'\"
$ !dark on green
$ d_g*COLOR == "''ESC_VT'PpS(M0(G),M7(D),M8(W),M15(W))''ESC_VT'\"
$ !dark on magenta
$ d_m*COLOR == "''ESC_VT'PpS(M0(M),M7(D),M8(W),M15(W))''ESC_VT'\"
$ !dark on cyan
$ d_c*COLOR == "''ESC_VT'PpS(M0(C),M7(D),M8(W),M15(W))''ESC_VT'\"
$ !dark on yellow
$ d_y*COLOR == "''ESC_VT'PpS(M0(Y),M7(D),M8(W),M15(W))''ESC_VT'\"
$!
$ !blue combinations
$ !red on blue
$ r_b*COLOR == "''ESC_VT'PpS(M0(B),M7(R),M8(W),M15(W))''ESC_VT'\"
$ !green on blue
$ g_b*COLOR == "''ESC_VT'PpS(M0(B),M7(G),M8(W),M15(W))''ESC_VT'\"
$ !yellow on blue
$ y_b*COLOR == "''ESC_VT'PpS(M0(B),M7(Y),M8(W),M15(W))''ESC_VT'\"
$ !cyan on blue
$ c_b*COLOR == "''ESC_VT'PpS(M0(B),M7(C),M8(W),M15(W))''ESC_VT'\"
$!
$ !blue on red
$ b_r*COLOR == "''ESC_VT'PpS(M0(R),M7(B),M8(W),M15(W))''ESC_VT'\"
$ !blue on green
$ b_g*COLOR == "''ESC_VT'PpS(M0(G),M7(B),M8(W),M15(W))''ESC_VT'\"
$ !blue on magenta
$ b_m*COLOR == "''ESC_VT'PpS(M0(M),M7(B),M8(W),M15(W))''ESC_VT'\"
$ !blue on cyan
$ b_c*COLOR == "''ESC_VT'PpS(M0(C),M7(B),M8(W),M15(W))''ESC_VT'\"
$ !blue on yellow
$ b_y*COLOR == "''ESC_VT'PpS(M0(Y),M7(B),M8(W),M15(W))''ESC_VT'\"
$!
$!green combinations
$ !red on green
$ r_g*COLOR == "''ESC_VT'PpS(M0(G),M7(R),M8(W),M15(W))''ESC_VT'\"
$ !green on red
$ g_r*COLOR == "''ESC_VT'PpS(M0(R),M7(G),M8(W),M15(W))''ESC_VT'\"
$!
$!extra combinations with red highlighting
$!cyan on black
$ c_d_r*COLOR == "''ESC_VT'PpS(M0(D),M7(C),M8(W),M15(R))''ESC_VT'\"
$!cyan on black
$ d_c_r*COLOR == "''ESC_VT'PpS(M0(C),M7(D),M8(W),M15(R))''ESC_VT'\"
$!cyan on blue
$ c_b_r*COLOR == "''ESC_VT'PpS(M0(B),M7(C),M8(W),M15(R))''ESC_VT'\"
$!cyan on blue
$ b_c_r*COLOR == "''ESC_VT'PpS(M0(C),M7(B),M8(W),M15(R))''ESC_VT'\"
$!cyan on blue
$ g_b_r*COLOR == "''ESC_VT'PpS(M0(B),M7(G),M8(W),M15(R))''ESC_VT'\"
$!cyan on blue
$ b_g_r*COLOR == "''ESC_VT'PpS(M0(G),M7(B),M8(W),M15(R))''ESC_VT'\"
$!blue on white
$ b_w_r*COLOR == "''ESC_VT'PpS(M0(W),M7(B),M8(W),M15(R))''ESC_VT'\"
$!white on blue
$ w_b_r*COLOR == "''ESC_VT'PpS(M0(B),M7(W),M8(W),M15(R))''ESC_VT'\"
$!yellow on blue
$ y_b_r*COLOR == "''ESC_VT'PpS(M0(B),M7(Y),M8(W),M15(R))''ESC_VT'\"
$!
$!***Setting X11 DECterm Window and Icon Titles***
$! first find node and process name for window title
$ node = F$TRNLNM("SYS$NODE")
$ procname = F$PROCESS()
$ title = "''node'''procname'"
$!
$! create symbols for setting window and icon titles
$ ESC[0,8]==27
$ window_title == "''ESC']21;''title'''ESC'\"
$ icon_title :== 'ESC']2L;'node''ESC'\
$!
$! EXAMPLE:
$! write sys$output window_title !to set window tile
$! write sys$output icon_title !to set icon title
$! set prompt "''window_title'$ " !to set DCL prompt
$!
$ EXIT
----------------------------cut-here-------------------------------------
Note: after running the above procedure, a...
$ SHOW SYMBOL *VT
will display the VT symbols which have been defined for you.
Here is an example DCL Procedure to show some of what can be done...
----------------------------cut-here-------------------------------------
CREATE TERM_DEMO.COM
$! Terminal Control DEMO
$!
$!define terminal screen control symbols
$ ESC[0,8]=27
$ ENQ[0,8]=5
$ LF[0,8]=10
$ CR[0,8]=13
$ CSI := "''ESC'["
$ DCS := "''ESC'P"
$ ES := "''ESC'[2J"
$ EStoEND := "''ESC'[0J"
$ EStoHERE := "''ESC'[1J"
$ ESline := "''ESC'[2K"
$ ESlinetoend := "''ESC'[0K"
$ ESlinetohere := "''ESC'[1K"
$ TOP := "''ESC'[H"
$ SWSH := "''ESC'#5" !Single Width Single Height
$ DW*SH := "''ESC'#6" !Double Width
$ DHT := "''ESC'#3" !Double Height Top
$ DHB := "''ESC'#4" !Double Height Bottom
$ NORM := "''ESC'[m"
$ BOLD := "''ESC'[1m"
$ UNDER := "''ESC'[4m"
$ BLINK := "''ESC'[5m"
$ INVERSE := "''ESC'[7m"
$ BOLDOFF := "''ESC'[22m"
$ UNDEROFF := "''ESC'[24m"
$ BLINKOFF := "''ESC'[25m"
$ INVERSEOFF := "''ESC'[27m"
$ ONEUP := "''ESC'[1A"
$ NEXTLINE := "''LF'''CR'"
$!
$ CURSORON:= "''CSI'?25h" !shows cursor
$ CURSOROFF:= "''CSI'?25l" !hides cursor
$!
$! initialize variables
$ SAY := WRITE SYS$OUTPUT
$ ER*ASE := WRITE SYS$OUTPUT ES,TOP
$ TERM_DEVICE = f$getdvi("TT","TT_PHYDEVNAM")
$ TERM_TYPE = f$extract(0,4,TERM_DEVICE)
$ TERM_WIDTH = f$getdvi("TT","DEVBUFSIZ")
$ TERM_HEIGHT = f$getdvi("TT","TT_PAGE")
$!
$ QSTR = "''INVERSE'Q''INVERSEOFF'"
$ CSTR = "''INVERSE'C''INVERSEOFF'"
$!
$ on control_y then goto askend
$ set term/inquire
$ set term/noecho
$ erase
$ say "''CSI'6;1H''CURSOROFF'" !move cursor to line 4 column 1
$ say "Terminal Device = ",TERM_DEVICE
$ say "Terminal Type = ",TERM_TYPE
$ say "Terminal Width = ",TERM_WIDTH
$ say "Terminal Height = ",TERM_HEIGHT
$!
$ say "''CSI'20;1H''CURSOROFF'" !move cursor to line 20 column 1
$ answer = ""
$ askstart:
$ say -
"''CSI'14;32H''ESline'''BLINK'answer = """,answer,"""''NORM'''CSI'20;1H"
$ say "''CSI'3;10H''ESline'''DW'''f$time()'''CSI'20;1H"
$ wait 00:00:00.50
$ READ /TIME_OUT=0/ERROR=askstart sys$command answer /PROMPT= -
"''CR'''ESline'''INVERSE'Press <Enter> to Stop''INVERSEOFF'"
$ say -
"''CSI'14;32H''ESline'''BLINK'answer = """,answer,"""''NORM'''CSI'20;1H"
$ askagain:
$ set term/echo
$ READ sys$command answer /PROMPT= -
"''CR'''ESline'''BOLD'Enter ''QSTR' to Quit, ''CSTR' to Cont.: ''NORM'"
$ set term/noecho
$ say -
"''CSI'14;32H''ESline'''BLINK'answer = """,answer,"""''NORM'''CSI'20;1H"
$ if f$edit(answer,"TRIM,UPCASE") .eqs. "Q" then goto askend
$ if f$edit(answer,"TRIM,UPCASE") .eqs. "C" then goto askstart
$ goto askagain
$ askend:
$ set term/echo
$ say "''CSI'22;20H" !move cursor to line 20 column 20
$ say "''CURSORON'That's all Folks!"
$ say ""
$ exit
----------------------------cut-here-------------------------------------
Cheers!
Keith Cayemberg |
|
| Back to top |
|
|
Gib Copeland
*nix forums beginner
Joined: 13 May 2005
Posts: 3
|
| Posted: Fri May 13, 2005 3:03 pm Post subject:
Re: vaxcluster vms v5.5-2 and v7.3
|
|
|
JF Mezei wrote:
| Quote: | Charlie Hammond wrote:
Here is an example the will illustrate how this implication may not work:
John loves Mary and Mary loves Bill.
Does this imply that John loves Bill?
It does imply that Bill will get John's diseases though (due to MSCP
ensuring that they are transfered between nodes in this 3 node cluster).
But this still doesn't explain what has changed in the SCS protocol to
cause 5.5-2 not to interact with 7.2.
Someone mentioned the volume shadowing code. Fine. But if you don't use
volume shadowing, would changes to it affect your ability to cluster ?
|
I'd guess nothing has changed in SCS that would prevent you getting
a basic cluster formed. But, SCS isn't the only thing that determines
whether various instances of VMS play well together in a cluster. If you
don't shadow, fine. If you don't use the queue manager, fine. If you're
not worried that changes to the lock manager, XQP or RMS might corrupt
your disks, fine. May work for you, just not supported. |
|
| Back to top |
|
|
Google
|
|
| Back to top |
|
|
|
|
The time now is Tue Dec 02, 2008 5:21 am | All times are GMT
|
|
Debt Help | Mobile Phones | Loans | Php Scripts | Debt Consolidation
|
|
Copyright © 2004-2005 DeniX Solutions SRL
|
|
|
|
Other DeniX Solutions sites:
Unix/Linux blog |
electronics forum |
medicine forum |
science forum |
|
|
Privacy Policy
|
Powered by phpBB © 2001, 2005 phpBB Group
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Forum index
»
Not Unix
»
VMS
