INFO-VAX Sun, 28 Sep 2008 Volume 2008 : Issue 523 Contents: Re: Enhancing DCL, was: Re: How do I add 2 letters to a long Re: Ordered media from hobbyist site but no action taken Re: quoting characters Re: What is a process' current WSxxxxx quotas ? ---------------------------------------------------------------------- Date: Sat, 27 Sep 2008 20:51:55 -0700 (PDT) From: AEF Subject: Re: Enhancing DCL, was: Re: How do I add 2 letters to a long Message-ID: <5880985a-8e44-45d2-b775-147349648c4a@u65g2000hsc.googlegroups.com> On Sep 26, 8:53 pm, clubley@remove_me.eisner.decus.org-Earth.UFP (Simon Clubley) wrote: > In article <54c74bd9-a1c5-4df0-863f-8a5169737...@m44g2000hsc.googlegroups.com>, AEF writes: > > > On Sep 24, 4:47=A0pm, koeh...@eisner.nospam.encompasserve.org (Bob > > Koehler) wrote: > >> In article , clubley@remove_me.eis= > > ner.decus.org-Earth.UFP (Simon Clubley) writes: > > >> > Automatic retention of command history, including the automatic merging= > > of > >> > just the new commands from that session into the command history file. > > >> =A0 =A0Command history retention in files has security implications. > > > I'd be quite happy with being with just being able to use RECALL/OUT > > in a command procedure. This way I could use my FILTER command > > procedure search for strings in the recall buffer. > > How would you handle merging the output from multiple simultaneous sessions > (assuming that the current command history was loaded at the start of the > session) ? I don't need to. And what does this have to do with placing RECALL/ OUT= in a command procedure? I want to be able to write the recall history buffer of my interactive session from a command procedure. There is nothing merged from anywhere else; this is the standard vendor-supplied DCL recall buffer we are talking about here. And where is the security problem? If I can run RECALL from a DCL prompt, how is that different -- security-wise -- from running the same from a command procedure? I'd also like to be able to use my FILTER command procedure to search for strings in the recall buffer. I have a command procedure called FILTER.COM with which I can SEARCH for strings from command output. Example: $ FILTER FELDMAN SH SYS %FILTER-I, SEARCHing for FELDMAN from $ SH SYS 000000AB FELDMAN CUR 4 159861 0 00:05:43.49 309166 662 $ FILTER.COM runs the command in P3 thru P8 to and directs its output to a temporary file called SYS$SCRATCH:REFILTER.TMP. Then it SEARCHes this temporary file for P2 and displays the results. The temporary file is left behind so that you can SEARCH it for other strings (assuming you want to SEARCH from the same original output, of course). OK, so what I want to do is use the FILTER procedure with the RECALL command. For example: $ FILTER DIRECTORY RECALL/ALL This would find and display all commands in the recall buffer that contain DIRECTORY. Mutliple sessions don't come into play at all. (I am running VMS V6.2, so please don't tell me to use PIPE and please don't tell me to upgrade. I have many reasons not to upgrade.) What does it mean "that the current command history was loaded at the start of the session"? How can there be a current command history for a session that hasn't started yet? Oh, perhaps you mean the current version of the file that holds all the commands entered in all previous sessions since the last time this history file was cleared? (I forgot that Unix (or at least some shells) does that.) To me, "current command history" means all the commands you've entered in your current session (hence the word "current" in "current history"). You and I have different interpretations of "current", "history", or both. I didn't realize that "current history" meant commands that were run in the "current" session *and* past sessions. OK. > In bash, only the commands entered during that session get appended to the > command history file. Why would it ever be done any other way? You mean there are shells out there, any of which reads one of these "history files" and then immediately regurgitates what it just read, appending it to the same "history file"? Huh? > That way you can have multiple simultaneous bash > sessions writing to the command history file without each running copy of > bash dumping it's own copy of the full command history into the history > file. > > > Yeah, let me guess: security implications. > > The way that I handle that in bash is to unset the history filename > variable so that the current session doesn't get written out if I've > used security related parameters on the command line. What does it mean to "unset the history filename variable"? And how do you do that so that it recognizes security-related params on the command line? This is a VMS newsgroup. Please do not assume such deep knowledge of Unix-type stuff. > > Simon. > > -- > Simon Clubley, clubley@remove_me.eisner.decus.org-Earth.UFP > Microsoft: Bringing you 1980's technology to a 21st century world AEF ------------------------------ Date: Sat, 27 Sep 2008 23:29:52 -0500 From: David J Dachtera Subject: Re: Ordered media from hobbyist site but no action taken Message-ID: <48DF0840.A903A184@spam.comcast.net> "vmsmangler@earthlink.net" wrote: > > I finally received a message from the Hobbyist site. He has been very > busy with his real job but he will be sending the media this weekend. > Thanks to everyone for their messages. > > Bill (aka VMS Manger) Indeed. Please remember that the VMS Hobbyist folks do this on a volunteer basis - they have real jobs that pay the bills and demand their attention at first priority. D.J.D. ------------------------------ Date: Sat, 27 Sep 2008 17:47:57 -0400 From: JF Mezei Subject: Re: quoting characters Message-ID: <48deaae7$0$12404$c3e8da3@news.astraweb.com> Michael Unger wrote: > Obviously you didn't read the ISO-8859-1 reference [1] mentioned > previously ... > [1] OK, so it is called different names. Some call it spacing acute. It appears that Microsoft has decided to use the spacing accent as closing single quote, and the normal apostrophe as opening quote or something to that effect. Note that for desktop publishing, there are many addition typographical encodings which are not part of ISO-8859-1 but are in the font encodings (which is what had confused me some) (opening/closing single quote and double quotes for instance). ------------------------------ Date: Sat, 27 Sep 2008 23:25:50 -0500 From: David J Dachtera Subject: Re: What is a process' current WSxxxxx quotas ? Message-ID: <48DF074E.1499A3F2@spam.comcast.net> "Main, Kerry" wrote: > > > -----Original Message----- > > From: David J Dachtera [mailto:djesys.no@spam.comcast.net] > > Sent: Saturday, September 20, 2008 12:49 AM > > To: Info-VAX@Mvb.Saic.Com > > Subject: Re: What is a process' current WSxxxxx quotas ? > > > > JF Mezei wrote: > > > > > > Is it just me in my ever-so-slightly-different universe, or is there > > no > > > way to obtain a process' current WSquota, WSextent etc values with > > SHOW > > > PROCESS ? > > > > > > [snip] > > > > > > I would like to know what the authorized WSEXTENT is for that job. > > > > From DCL, no - nothing "easy". > > > > Try SDA (ANALYZE/SYSTEM) and SHOW PROCESS within SDA to view the > > current > > quotas and usage information. > > > > D.J.D. > > As mentioned in my earlier reply: > > On VMS V8.3+ Alpha/Integrity - > > $ Show Proc x/cont > Hit W (from memory, or Q? to flip back and forth) Didn't want to make any brash assumptions about his VMS version... D.J.D. ------------------------------ End of INFO-VAX 2008.523 ************************