1 INFO-VAX	Mon, 26 Jun 2006	Volume 2006 : Issue 353       Contents: Re: Alpha remembrance day  Re: Alpha remembrance day  Re: APACHE$PRIVILEDGED Re: APACHE$PRIVILEDGED Re: charon-vax on linux  Re: charon-vax on linux ) Command Line Commands And Editor Commands - Re: Command Line Commands And Editor Commands - Re: Command Line Commands And Editor Commands - Re: Command Line Commands And Editor Commands - Re: Command Line Commands And Editor Commands : Education Ministry rethinks payroll plans (Oracle and VMS)> Re: Education Ministry rethinks payroll plans (Oracle and VMS)> Re: Education Ministry rethinks payroll plans (Oracle and VMS)C Re: How to run program in background. How to list my processies and P Re: How to run program in background. How to list my processies and kill  a runnP How to run program in background. How to list my processies and kill a running pP Re: How to run program in background. How to list my processies and kill a runni0 Links to show how to use the source code editors4 Re: Links to show how to use the source code editors4 Re: Links to show how to use the source code editors8 Re: Stacks, Static, Item Lists, Modes and Initialization Vax Debugger Examples  Re: Vax Debugger Examples  [ECP] OpenVMS V8 Re: [ECP] OpenVMS V8  F ----------------------------------------------------------------------    Date: 26 Jun 2006 02:20:46 -0700 From: etmsreec@yahoo.co.uk" Subject: Re: Alpha remembrance dayC Message-ID: <1151313646.152283.264050@y41g2000cwy.googlegroups.com>    Well, that's one view.  D Alpha was, although strong, a minority player in the CPU field.  CanG you say "lack of applications"?  Can you say "lack of operating systems  to run on it"?  F Compaq's main field of work was PeeCees before the purchase of DigitalA and Tandem.  Compaq really didn't know how to integrate these two F enterprise-based corporations into their PC-based corporation.  So, ifF the merger with HP hadn't happened, it could be that we'd be left withE a lot less than VMS on Integrity with support of VMS on Alpha and VAX  moving forward.   E Digital was a sick puppy when Compaq bought its remains.  Compaq just D didn't realize it until the deal was done.  HP made the same mistake with the Compaq merger.   0 Be careful what you wish for - it may come true.   Steve & (speaking for himself and nobody else)   JF Mezei wrote: C > It was 5 years ago today that the IT equivalent of a war criminal E > committed the genocide of a perfectly healthy computer acrhitecture 4 > based on his ethnicity (Digital instead of Intel). > # > June 25 2001, the day Alpha died.  >  > G > It was on June 25 2001 that Michael "Curly" Capellas, then CEO of the J > now defunct Compaq Computer Corporation announced the death sentence forE > Alpha. It was guilty of competing against Intel and giving Compaq a D > technological edge over Intel, Compaq's main strategic supplier ofF > chips. Compaq mutilated itself to maintain its friendhip with Intel. >  > E > It is now known that Capellas had already engaged negotiations with A > Carleton "Carly" Fiorina, then CEO of HP for HP to purchase the F > leftovers of Compaq that had been without stewardship since Curly, aD > simple accountant, was asked to become CEO because nobody else had+ > wanted the job after Pfeiffer was ousted.  >  > 2 > June 25 2001, the day Capellas euthanised Alpha. >  > H > Michael "Curly" Capellas takes a prominent spot on the Digital Hall ofF > Shame, along with his peer Robert Palmer who suffocated Digital intoG > extinction. Hopefully one day, both can be tried at the International F > Computer Court in The Hague with Curly charged with  genocide of theK > Alpha architecture. Both  should be held accountable for their IT crimes.  >  > 9 > June 25 2001, the day customers were wounded by Compaq.  > F > The strength of Alpha is clearly visible today, 5 years after it wasH > injected with the deadly venom: Alpha is still popular and competitiveG > in the computer industry.   Mark Hurd, current CEO of HP, will commit G > another computer crime this october when he will prohibit the sale of E > new Alpha computers, despite there still being a healthy demand for  > Alpha systems. > H > June 25 2001, the day Compaq (and now HP) lost the trust of customers. > H > Murdering a perfectly functional and highly performant and establishedH > architecture in order to help a  malformed baby nobody wants. Where'reH > the logic ? An abortion should have been performed on that IA64 misfit> > instead of the genocide on a perfectly healthy architecture. >  > J > June 25 2001, the day Alpha engineers got an arrow shot into their heart > and sold to the devil. >  > G > 5 years ago today, a grave injustice was committed. While we can hope G > the guilty will be tried and punished for their crime, we must take a I > minute  to remember Alpha, the great chip architecture that lead the IT A > world in performance for so many years and whose brief life was  > terminated at its prime. > G > And we must also remember all the engineers who had worked so hard to I > build that great architecture and developped so many features that lead  > the industry.  >  > I > We should each take a minute to remember Alpha, our dear beloved friend F > today.  There is some comfort in that, while the architecture may beH > dead and unable to produce more Alphas, existing Alphas will likely go > to heaven (hobbyists!)...  >  >  > IN MEMORIAM. > J > Alpha. Killed 5 years ago by Michael Capellas in a hainous crime against > the IT industry.   ------------------------------  + Date: Mon, 26 Jun 2006 12:15:46 +0000 (UTC)  From: david20@alpha2.mdx.ac.uk" Subject: Re: Alpha remembrance day) Message-ID: <e7oj5i$jh8$1@news.mdx.ac.uk>   ` In article <1151313646.152283.264050@y41g2000cwy.googlegroups.com>, etmsreec@yahoo.co.uk writes: >Well, that's one view.  > E >Alpha was, although strong, a minority player in the CPU field.  Can H >you say "lack of applications"?  Can you say "lack of operating systems >to run on it"?  >   L At the time of the Compaq purchase of Digital, Alpha supported a respectable number of Operating Systems :-   Windows  Linux (multiple distributions) NetBSD OpenBSD  FreeBSD  VMS  and  TRU64     L (I even saw Linux on Alpha distributions for sale in a number of high streetC shops - which was pretty unusual for most non-intel distributions).     
 David Webb Security team leader CCSS Middlesex University                    G >Compaq's main field of work was PeeCees before the purchase of Digital B >and Tandem.  Compaq really didn't know how to integrate these twoG >enterprise-based corporations into their PC-based corporation.  So, if G >the merger with HP hadn't happened, it could be that we'd be left with F >a lot less than VMS on Integrity with support of VMS on Alpha and VAX >moving forward. > F >Digital was a sick puppy when Compaq bought its remains.  Compaq justE >didn't realize it until the deal was done.  HP made the same mistake  >with the Compaq merger. > 1 >Be careful what you wish for - it may come true.  >  >Steve' >(speaking for himself and nobody else)  >  >JF Mezei wrote:D >> It was 5 years ago today that the IT equivalent of a war criminalF >> committed the genocide of a perfectly healthy computer acrhitecture5 >> based on his ethnicity (Digital instead of Intel).  >>$ >> June 25 2001, the day Alpha died. >> >>H >> It was on June 25 2001 that Michael "Curly" Capellas, then CEO of theK >> now defunct Compaq Computer Corporation announced the death sentence for F >> Alpha. It was guilty of competing against Intel and giving Compaq aE >> technological edge over Intel, Compaq's main strategic supplier of G >> chips. Compaq mutilated itself to maintain its friendhip with Intel.  >> >>F >> It is now known that Capellas had already engaged negotiations withB >> Carleton "Carly" Fiorina, then CEO of HP for HP to purchase theG >> leftovers of Compaq that had been without stewardship since Curly, a E >> simple accountant, was asked to become CEO because nobody else had , >> wanted the job after Pfeiffer was ousted. >> >>3 >> June 25 2001, the day Capellas euthanised Alpha.  >> >>I >> Michael "Curly" Capellas takes a prominent spot on the Digital Hall of G >> Shame, along with his peer Robert Palmer who suffocated Digital into H >> extinction. Hopefully one day, both can be tried at the InternationalG >> Computer Court in The Hague with Curly charged with  genocide of the L >> Alpha architecture. Both  should be held accountable for their IT crimes. >> >>: >> June 25 2001, the day customers were wounded by Compaq. >>G >> The strength of Alpha is clearly visible today, 5 years after it was I >> injected with the deadly venom: Alpha is still popular and competitive H >> in the computer industry.   Mark Hurd, current CEO of HP, will commitH >> another computer crime this october when he will prohibit the sale ofF >> new Alpha computers, despite there still being a healthy demand for >> Alpha systems.  >>I >> June 25 2001, the day Compaq (and now HP) lost the trust of customers.  >>I >> Murdering a perfectly functional and highly performant and established I >> architecture in order to help a  malformed baby nobody wants. Where're I >> the logic ? An abortion should have been performed on that IA64 misfit ? >> instead of the genocide on a perfectly healthy architecture.  >> >>K >> June 25 2001, the day Alpha engineers got an arrow shot into their heart  >> and sold to the devil.  >> >>H >> 5 years ago today, a grave injustice was committed. While we can hopeH >> the guilty will be tried and punished for their crime, we must take aJ >> minute  to remember Alpha, the great chip architecture that lead the ITB >> world in performance for so many years and whose brief life was >> terminated at its prime.  >>H >> And we must also remember all the engineers who had worked so hard toJ >> build that great architecture and developped so many features that lead >> the industry. >> >>J >> We should each take a minute to remember Alpha, our dear beloved friendG >> today.  There is some comfort in that, while the architecture may be I >> dead and unable to produce more Alphas, existing Alphas will likely go  >> to heaven (hobbyists!)... >> >> >> IN MEMORIAM.  >>K >> Alpha. Killed 5 years ago by Michael Capellas in a hainous crime against  >> the IT industry.  >    ------------------------------    Date: 26 Jun 2006 01:00:01 -0700  From: "Ian Miller" <ijm@uk2.net> Subject: Re: APACHE$PRIVILEDGED C Message-ID: <1151308801.289552.129000@p79g2000cwp.googlegroups.com>   9 After an extensive search lasting several seconds I found   F http://h71000.www7.hp.com/openvms/products/ips/apache/csws_source.html    See if it contains what you seek   ------------------------------  # Date: Mon, 26 Jun 2006 15:15:59 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com> Subject: Re: APACHE$PRIVILEDGED 1 Message-ID: <PSSng.2241$AH2.217@news.cpqcorp.net>   A So I'm the designated tall poppy?  I'm flattered; thank you.  :-)   > Some background on security and privileged application code...  C The primary security on OpenVMS and on most other multi-processing  G operating systems is implemented via the memory management system (the  F page tables) and via what VAX calls the change-mode routines, via the D Alpha SRM PALcode change-mode equivalent, or via what the IA-32 and F IA-32e architectures refer to as the call gate.  The operating system I protects itself by restricting access into the inner memory access modes   and to the pages of memory.   G With any privileged code, the code has to ensure that an accidental or  E induced corruption in shared resources does not compromise security.  D Most folks working with such a construct know to probe the argument A lists, though a few folks might well miss the second-level probe  I involved when descriptors or such are involved within the argument list.  F   Far more subtle (but no less hazardous) can be security attacks via D intentionally or unintentionally shared resources, such as the imageI pool (if and as applicable) or (again, if applicable) the stack.  One of  D the most subtle attacks is to either induce a run-time error within H inner-mode code, or (worse) to fully hijack the inner-mode code.   This E is the usual target intent for a buffer-overrun attack, obviously --  0 either to destabilize the code, or to hijack it.  @ With OpenVMS constructs including device drivers (or drivers an D ancillary control processes (ACPs))and user-written system services D (UWSS; also known as privileged shareable images), these constructs D operate in inner processor modes.  (I'll leave execlets for another C day.)  Device drivers and UWSS interfaces both have APIs, with the  H former built into and through $qio[w] and $io_perform[w] and the latter H using the so-called privileged library vector and the associated change  mode handlers.  F Drivers, ACPs, UWSS images and execlets are all part of the so-called E trusted computing base (TCB), and such hunks of code are accordingly  , responsible for maintaining system security.  E The device driver interface provides routines that probe buffers for  E read or read and write access, while the UWSS interface requires the  H code more directly perform the probes using built-ins, PALcode calls or @ such.  Performing the individual argument list and buffer probe C operations is easy.  Determining and performing all of the various  @ potential cases in a non-trivial argument list is somewhat more > involved.  Code must also buffer information in a trusted areaH as required and/or must re-probe the arguments upon completion to avoid E having the argument list to avoid attacks based on changing the data.   D One of the more hazardous situations for system security is a mixed B environment; where there are resources shared between trusted and F untrusted environments.  On an OpenVMS system, this can include ASTs, A the heap, the stack, argument lists, or -- such as in a threaded  F environment -- most anything.  Here, as with most other environments, I the memory page protections are your best resource.  But within the same  F address space of a process, this can be more difficult than it seems. B For UWSS code that uses RTL services, for instance, attacks can beD via deliberately-induced heap or stack corruptions, or even through F hijacking the contents of unprotected pages.  Context arguments often I used in multi-part calls are and must be carefully secured, and the code  B must be willing and able to accept any corruptions to the values. I (Drivers can tend to avoid the need  for context arguments by being able  , to store data in trusted regions of memory.)  H And probably the most hazardous environment is where application code isI performing security-related functions, such as authentication or evasion.   I As for the UWSS, calling into a routine that isn't intended to be called  C from privileged environments can open up various subtle exposures.  H Installing an executable image, for instance, and specifically an image F that wasn't intended to be installed, can cause security exposures as G the tool might be able to read or write files or objects not otherwise  I accessible.  Not only will the operation that requires privileges now be  G permitted, but other and potentially unintended operations can also be  H permitted.  This is where a security investigation into the called code I can be potentially involved, as well -- since the called code may or may  D not expect the inner-mode call, you need to ensure it will function I correctly for your environment.  (If the environment has untrusted users  !   and if it needs to be secured.)   I If you can trust the calling environment -- and anybody that can link to  E an activate the UWSS when installed -- then the coding involved in a  H UWSS is trivial.  (If I trust the calling code but not the environment, I then I tend to install the executable image with privileges.  If I can't  A trust the calling code (or the environment), then I start to get  I seriously paranoid.  This can be a UWSS, a driver or a driver and ACP --  F as has been obvious in variations of this thread, I tend to prefer to H call RTL services from user-mode, for instance, and an ACP or an AST is  the usual path.)  B Now as to what other folks might choose here and how a particular H programmer might choose to implement something, well, that's up to them.  F And Mr Maher, are you going to submit your FAKE_VM tool update to the H OpenVMS Freeware?  We're past the deadline, but if you can get the tool F packaged and submitted Real Soon Now, I can add it into the packaging  that's presently underway.   ------------------------------    Date: 26 Jun 2006 01:17:08 -0700  From: "Ian Miller" <ijm@uk2.net>  Subject: Re: charon-vax on linuxC Message-ID: <1151309828.284358.140200@m73g2000cwd.googlegroups.com>    Information is available at . http://www.softresint.com/charon-vax/index.htm  " or you can contract them directly.0 http://www.softresint.com/representations.htm#na  8 There are a range of resellers of this product listed at  8 http://www.softresint.com/charon-vax/CHARON_partners.htm   ------------------------------    Date: 26 Jun 2006 01:33:56 -0700  From: "Ian Miller" <ijm@uk2.net>  Subject: Re: charon-vax on linuxC Message-ID: <1151310836.388821.193010@i40g2000cwc.googlegroups.com>    Information is available at . http://www.softresint.com/charon-vax/index.htm  " or you can contract them directly.0 http://www.softresint.com/representations.htm#na  8 There are a range of resellers of this product listed at  8 http://www.softresint.com/charon-vax/CHARON_partners.htm   ------------------------------    Date: 26 Jun 2006 04:43:49 -0700$ From: "Chris L" <clusardi2k@aol.com>2 Subject: Command Line Commands And Editor CommandsC Message-ID: <1151322229.031448.233310@p79g2000cwp.googlegroups.com>    Hello,  )     I used to use vax/vms for many years.   D     I have just ordered a few books on these commands but would likeF links to Internet sites that list and explain the ones that I would be0 using as a programmer at the command line level.  
    Thank you,     Christopher Lusardi   ------------------------------    Date: 26 Jun 2006 06:21:37 -0700$ From: "Chris L" <clusardi2k@aol.com>6 Subject: Re: Command Line Commands And Editor CommandsC Message-ID: <1151328097.143886.199980@y41g2000cwy.googlegroups.com>    Richard B. Gilbert wrote:  > Chris L wrote: > 
 > > Hello, > > - > >     I used to use vax/vms for many years.  > > H > >     I have just ordered a few books on these commands but would likeJ > > links to Internet sites that list and explain the ones that I would be4 > > using as a programmer at the command line level. > >  > >    Thank you,  > >    Christopher Lusardi > >  > B > It's not that difficult!   Use HELP to refresh your memory.  TheE > commands you are most likely to need are EDIT, PRINT, (CC, FORTRAN, G > COBOL, BASIC,etc to compile) LINK to link your program and RUN to run I > it.  I still use the EDT editor but, if you have to learn an editor you K > should probably learn EDIT.  And you will need to learn or relearn DEBUG.   @ I woun't have access to a Vax system for a few months. I want to
 re-learn them B before I actually begin using the commands. Do you have any links?   Thanks,  Christopher Lusardi    ------------------------------  % Date: Mon, 26 Jun 2006 09:15:46 -0400 3 From: "Richard B. Gilbert" <rgilbert88@comcast.net> 6 Subject: Re: Command Line Commands And Editor Commands: Message-ID: <Sp-dnTpJvcieQwLZnZ2dnUVZ_q2dnZ2d@comcast.com>   Chris L wrote:   > Hello, > + >     I used to use vax/vms for many years.  > F >     I have just ordered a few books on these commands but would likeH > links to Internet sites that list and explain the ones that I would be2 > using as a programmer at the command line level. >  >    Thank you,  >    Christopher Lusardi >   A It's not that difficult!   Use HELP to refresh your memory.  The  D commands you are most likely to need are EDIT, PRINT, (CC, FORTRAN, F COBOL, BASIC,etc to compile) LINK to link your program and RUN to run H it.  I still use the EDT editor but, if you have to learn an editor you I should probably learn EDIT.  And you will need to learn or relearn DEBUG.    ------------------------------    Date: 26 Jun 2006 06:25:06 -0700  From: "Ian Miller" <ijm@uk2.net>6 Subject: Re: Command Line Commands And Editor CommandsC Message-ID: <1151328306.912925.218390@y41g2000cwy.googlegroups.com>   $ VMS help is available via a web site! http://www.openvms-rocks.com/Help   D Or why not sign up for a free account and have a play - this cluster has a vax and an alpha in it  ) http://www.openvms-rocks.com/signup.shtml    ------------------------------  # Date: Mon, 26 Jun 2006 15:21:14 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>6 Subject: Re: Command Line Commands And Editor Commands2 Message-ID: <KXSng.2242$2y2.2094@news.cpqcorp.net>   Chris L wrote:  + >     I used to use vax/vms for many years.  > F >     I have just ordered a few books on these commands but would likeH > links to Internet sites that list and explain the ones that I would be2 > using as a programmer at the command line level.  F    The OpenVMS manuals including the User's Guide and the Programming H Concepts Manuals and the language-specific users' and reference manuals  are available at:   $    http://www.hp.com/go/openvms/doc/  E    Bibliographies, introductions, tutorials, presentations, etc, are   available in the OpenVMS FAQ:   $    http://www.hp.com/go/openvms/faq/  ;    The FAQ is easiest to search in the text-format version.    ------------------------------  % Date: Mon, 26 Jun 2006 08:55:09 -0400 2 From: "Stanley F. Quayle" <squayle@insight.rr.com>C Subject: Education Ministry rethinks payroll plans (Oracle and VMS) : Message-ID: <449FA0ED.5056.1DE32E1@squayle.insight.rr.com>  D *sigh* Here's another customer who thought that support for VMS had  ended...  9    http://www.stuff.co.nz/stuff/0,2106,3711102a28,00.html   @ He says that at the time a decision was made to change systems, B Datapay's Oracle database and VMS operating system were no longer ; supported by vendors. This "represented a high risk to the   Government", he says.     
 --Stan Quayle  Quayle Consulting Inc.  
 ----------8 Stanley F. Quayle, P.E. N8SQ  Toll free: 1-888-I-LUV-VAX3 8572 North Spring Ct., Pickerington, OH  43147  USA < stan-at-stanq-dot-com   http://www.stanq.com/charon-vax.html) "OpenVMS, when downtime is not an option"    ------------------------------    Date: 26 Jun 2006 06:33:16 -0700  From: "Ian Miller" <ijm@uk2.net>G Subject: Re: Education Ministry rethinks payroll plans (Oracle and VMS) C Message-ID: <1151328796.897399.123730@b68g2000cwa.googlegroups.com>    and later it says   F "Those concerns have been resolved now that support for Oracle and VMSA has been extended and Mr Cholewa says the option of the Education - Ministry upgrading Datapay has been revived."   H Hopefully this means someone in local hp land woke up and educated them.   ------------------------------  % Date: Mon, 26 Jun 2006 12:58:49 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> G Subject: Re: Education Ministry rethinks payroll plans (Oracle and VMS) , Message-ID: <44A01249.F04E9281@teksavvy.com>   Ian Miller wrote: H > "Those concerns have been resolved now that support for Oracle and VMSC > has been extended and Mr Cholewa says the option of the Education / > Ministry upgrading Datapay has been revived."     B Support should not have been "extended".  They should have clearlyI stated that there never had been any thoughts of ending support. Period.      D If you want to kill rumours of VMS being desupported, you don't justF extend support from year to year, you use the media to kill the rumourG once and for all. They may have rescued that one account for a few more , years, but they missed a golden opportunity.   ------------------------------    Date: 26 Jun 2006 12:03:50 -0500 From: briggs@encompasserve.orgL Subject: Re: How to run program in background. How to list my processies and3 Message-ID: <+i7nWu8Hzc4V@eisner.encompasserve.org>   a In article <ncTng.2245$hJ2.1424@news.cpqcorp.net>, Hoff Hoffman <hoff-remove-this@hp.com> writes:  > Chris L wrote: > % >>      How would I do this on a vax?  > H >    OpenVMS VAX does not have the concept of foreground and background  > processes, that's Unix.    >  >    As for process control: > ; >    RUN/DETACH, SUBMIT, sys$creprc, lib$spawn, SPAWN, etc.     I would add ATTACH to this list.  C Note that SPAWN [/NOWAIT] and ATTACH allow you to achieve _some of_ @ the effects of foreground and background processes and switching among them.   4 If you have virtual terminals enabled, you can also:  & $ CONNECT VTAxxx [/CONTINUE] [/LOGOUT]   and    $ DISCONNECT [/CONTINUE]   >    As for process display: > $ >    SHOW SYSTEM, SHOW PROCESS, etc.  7 If you're using SPAWN and ATTACH, use SHOW PROCESS /SUB   D If using DISCONNECT and CONNECT, use SHOW USER <your-user-name-here>   >    As for deleting a process:  >  >    STOP/ID  C Note that applications that make use of a terminal mailbox (used to D capture terminal event notification such as unsolicited input, modemH hangup and the like) run afoul of the restriction that there can be onlyH one mailbox associated with a particular terminal device.  This can poseC problems if you try to use SPAWN and ATTACH with such applications.   B In addition, VMS subprocesses are not allowed to survive the deathA of their parents.  This is not something that can be papered over > with a "nohup".  If you log out of your main process, all yourF "background" subprocesses at all levels _will_ be killed first.  There5 is no such thing as an orphaned subprocess under VMS.   C Finally, SPAWN and ATTACH do not support the notion of a background D process executing until it needs terminal I/O and then pausing.  You only get two choices:   C 1.  SPAWN /WAIT -- the creator goes to sleep (hibernates) until the A     child goes away or uses ATTACH to re-activate the creator and #     put the child into hibernation.   ? 2.  SPAWN /NOWAIT -- both creator and child go on executing and <     sharing terminal access.  Shared terminal access betweenF     two active processes can be bewildering.  This is probably a large1     part of the reason that /WAIT is the default.   H If you want a process to keep running until it needs to do some terminalB I/O then virtual terminals and the CONNECT and DISCONNECT commands0 may fit your needs better than SPAWN and ATTACH.  G But you may find that simply keeping multiple terminal emulator windows  open is easier.    ------------------------------  % Date: Mon, 26 Jun 2006 13:07:26 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> Y Subject: Re: How to run program in background. How to list my processies and kill  a runn , Message-ID: <44A0144C.F4A52DC2@teksavvy.com>  E To run a program in the background, the best bet is to submit it to a  batch queue.  4 $HELP SUBMIT  tells you about all the possibilities.G $HELP Queues  gives you an overview of the various commands that affect  queues and jobs within queues   J $SHOW ENTRY will tell you all the batch jobs that are under your username.  F SUBMIT   requires a DCL command file ( typically something.COM ). AKA:= something you would invoke with @SOMETHING.COM interactively.   G The SPAWN command allows you to more or less clone your current process * and run a new command. YOu may wish to useF SPAWN/NOWAIT/OUTPUT=xxx/INPUT=yyy if you want the command to truly run! in background and not bother you.   B There is also the RUN/PROC=name  image.exe  command. This will runG IMAGE.EXE as a detached process. But it does not inherit access to DCL, B and many applications do not like this since they won't be able toF translate DCL symbols, or use the callable "SPAWN" routines. There areH ways around this, but it becomes a lot easier to just submit a batch job@ than getting a detached process setup with FULL DCL environment.  B (you can search this newsgroup for RUN /DETACHED  LOGINOUT and youP should then get examples of how to setup a detached process that has DCL access.   ------------------------------    Date: 26 Jun 2006 07:42:41 -0700$ From: "Chris L" <clusardi2k@aol.com>Y Subject: How to run program in background. How to list my processies and kill a running p C Message-ID: <1151332961.460060.131490@i40g2000cwc.googlegroups.com>    Hello,  "      How would I do this on a vax?  
 Thank you, Christopher Lusardi    ------------------------------  # Date: Mon, 26 Jun 2006 15:38:59 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com>Y Subject: Re: How to run program in background. How to list my processies and kill a runni 2 Message-ID: <ncTng.2245$hJ2.1424@news.cpqcorp.net>   Chris L wrote:  $ >      How would I do this on a vax?  F    OpenVMS VAX does not have the concept of foreground and background  processes, that's Unix.       As for process control:  9    RUN/DETACH, SUBMIT, sys$creprc, lib$spawn, SPAWN, etc.       As for process display:  "    SHOW SYSTEM, SHOW PROCESS, etc.      As for deleting a process:   
    STOP/ID  E    The OpenVMS HELP library (once you get your system, or should you  D have access to another OpenVMS system) and the User's Guide and the G Programming Concepts manuals can be quite useful.  The OpenVMS FAQ has  I pointers to network-accessible OpenVMS systems where you can sign up for  F a free username, as well, so you can start your work and your testing $ and your HELP file access right now.  $    http://www.hp.com/go/openvms/doc/$    http://www.hp.com/go/openvms/faq/   ------------------------------    Date: 26 Jun 2006 08:07:45 -0700$ From: "Chris L" <clusardi2k@aol.com>9 Subject: Links to show how to use the source code editors B Message-ID: <1151334465.033078.76420@p79g2000cwp.googlegroups.com>  C Is there a link that will show me the commands I can use within the  editors?   Thanks,  Christopher Lusardi    ------------------------------    Date: 26 Jun 2006 09:35:45 -0700  From: "Ian Miller" <ijm@uk2.net>= Subject: Re: Links to show how to use the source code editors A Message-ID: <1151339745.134263.4020@y41g2000cwy.googlegroups.com>    See 4 http://seqaxp.bio.caltech.edu/vms_beginners_faq.html    http://www.hp.com/go/openvms/faq   and consider this bookB http://www.amazon.com/exec/obidos/ASIN/1555582796/ref=ase_tru64org  E Best thing would be to get an account on a free VMS system and gave a  go.    Try  http://deathrow.vistech.net/ or http://www.encompasserve.org/  or http://polarhome.com/    ------------------------------  % Date: Mon, 26 Jun 2006 13:09:40 -0400 - From: JF Mezei <jfmezei.spamnot@teksavvy.com> = Subject: Re: Links to show how to use the source code editors , Message-ID: <44A014D1.DB25E4FD@teksavvy.com>   Chris L wrote: > E > Is there a link that will show me the commands I can use within the 
 > editors?    B http://www.hp.com/go/vms/doc   and hunt down the documentation for( TPU/EVE within the VMS operating system.  H Alternatively, start your editor, and press the HELP key (F15 on top rowH of function keys).  You'll get plenty of help on all the commands there.   ------------------------------  # Date: Mon, 26 Jun 2006 14:34:57 GMT & From: John Reagan <john.reagan@hp.com>A Subject: Re: Stacks, Static, Item Lists, Modes and Initialization 2 Message-ID: <lgSng.2239$ZG2.1548@news.cpqcorp.net>   Richard Maher wrote:  L > Now I'm not too bright with Bliss but my mate assures me that "Local" goesC > on the Stack and "Own" looks like static compiler generated data.   G I don't know anything about the code of which you speak, but I do know   BLISS.  J OWN is indeed static, local storage.  LOCAL is indeed stack-based storage.  I The INITIAL and PRESET attributes tell BLISS to initialize the variables  D when they are created.  For OWN, that is done conceptually at image I activation time although the initialization was probably done at compile  E or link time.  For LOCAL, each time the routine containing the LOCAL  9 (with INITIAL or PRESET), that variable gets initialized.   D The contents of local variables when a routine exits is outside the I definition of BLISS (or C for that matter).  If your BLISS or C tries to  F zero out a local variable as the last operation in a routine, you are B likely to find the compiler's optimizer removing the operation as  unnecessary.   --   John Reagan / HP Pascal/{A|I}MACRO for OpenVMS Project Leader  Hewlett-Packard Company    ------------------------------    Date: 26 Jun 2006 08:00:25 -0700$ From: "Chris L" <clusardi2k@aol.com> Subject: Vax Debugger ExamplesB Message-ID: <1151334024.931867.30400@p79g2000cwp.googlegroups.com>  C Is there a link that can show me how to debug programs? A link that D shows how to step through a program, how to set break points, how toD set program variables, etc. I'm looking for all the goodies that the vax debugger does.   Thanks,  Christopher Lusardi    ------------------------------  % Date: Mon, 26 Jun 2006 11:13:26 -0400 # From: sol gongola <sol@adldata.com> " Subject: Re: Vax Debugger Examples0 Message-ID: <1151334861.804023@nntp.acecape.com>   Chris L wrote:E > Is there a link that can show me how to debug programs? A link that F > shows how to step through a program, how to set break points, how toF > set program variables, etc. I'm looking for all the goodies that the > vax debugger does. > 	 > Thanks,  > Christopher Lusardi  > 5 Google for "vms debugger" gave me these among others: R http://www.njit.edu/v2/Directory/Admin/CSD/Academic_Computing/Manuals/VMS/vms.html7 http://h71000.www7.hp.com/DOC/73final/4538/4538PRO.HTML B http://www.mathsci.appstate.edu/~crr/cs2440/oldexamples/debug.html   ------------------------------    Date: 26 Jun 2006 16:38:31 -02006 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOEGER) Subject: [ECP] OpenVMS V8 , Message-ID: <44a00d87$1@news.langstoeger.at>  ; http://www.openvms.digital.com/openvms/products/ecp/ states   G   For Alpha systems running OpenVMS Version 8.2 and later, the ECP Data L   Collector is replaced by the Performance Data Collector for OpenVMS (TDC).G   TDC is installed with OpenVMS and not distributed with ECP. For Alpha K   systems running OpenVMS Version 7.3-2, data can be collected using either J   ECP Data Collector or TDC. For Alpha systems running earlier versions ofL   OpenVMS, and for VAX systems running OpenVMS Version 7.3 and earlier, onlyJ   the ECP Collector is available for data collection. The ECP Analyzer canH   process files created by Version 2.1 and later of the Performance DataL   Collector. Further information about the Performance Data Collector can be   found at URL:   )   http://www.hp.com/products/openvms/tdc/   H while http://www.openvms.digital.com/openvms/os/swroll/VAROL.HTML states  L   Enterprise Capacity  5.5     6.2   8.2      NOW        25.01 606AA Y  X  X   Planner Analyzer   L   Enterprise Capacity  5.5     6.2   8.2      NOW        25.01 604AA Y  X  X   Planner Data Collector  L Which one is correct? Is ECP V5.5 collector supported on OpenVMS Alpha V8.2?  H I currently believe that the VAROL is in error (and ECP Collector is notM running/supported on V8.2 - while ECP Analyzer is, but needs reinstallation), > but I so far haven't tried it (2Bsure). Has anybody more info?  = Btw: ECP is on V5.5A, not V5.5 (or is there already a newer?)    TIA   L PS: If ECP is still there, and on V8, could it be changed to PCSI, please... --   Peter "EPLAN" LANGSTOEGER % Network and OpenVMS system specialist  E-mail  peter@langstoeger.atF A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist   ------------------------------  # Date: Mon, 26 Jun 2006 15:29:56 GMT , From: Hoff Hoffman <hoff-remove-this@hp.com> Subject: Re: [ECP] OpenVMS V8 1 Message-ID: <U3Tng.2244$zH2.542@news.cpqcorp.net>   H    TDC is the newer package, and ECP is the older.  There is an overlap G in the OpenVMS versions supported.  I'll pass your report of confusion  E along to the folks that manage the resources involved for resolution.    ------------------------------   End of INFO-VAX 2006.353 ************************