1 INFO-VAX	Mon, 19 Jun 2006	Volume 2006 : Issue 339       Contents:" Re: Compiling Problem with LibCurl* Re: create and modify user, but not delete% Re: How can I read a locked VMS file? % Re: How can I read a locked VMS file? 0 Re: Just Ask The Vendor: Can OpenVMS Scale Down?0 Re: Just Ask The Vendor: Can OpenVMS Scale Down?0 Re: Just Ask The Vendor: Can OpenVMS Scale Down?# Re: Open VMS OS recovery on Itanium & Re: Problem with "New mail" broadcastsI Re: Q: (long) DCL symbols not appearing in Show Symbol output [SLS V2.9H] P Re: Q: (long) DCL symbols not appearing in Show Symbol output [SLS V2.9H] [SLS V$ Re: Sending HTML mail from VMS MAIL?  F ----------------------------------------------------------------------    Date: 19 Jun 2006 11:58:50 -05004 From: kuhrt.nospammy@encompasserve.org (Marty Kuhrt)+ Subject: Re: Compiling Problem with LibCurl 3 Message-ID: <AcA4HkubqgBk@eisner.encompasserve.org>   e In article <4488d258$0$26888$88260bb3@free.teranews.com>, Tim Sneddon <tesneddon@bigpond.com> writes:  > Marty Kuhrt wrote:D >> While I provide the .olb* files in the VMS cURL distribution, youG >> will need the source kit to build something that references the cURL G >> include files.  I did this so that if someone wanted to build a cURL F >> app they didn't have to compile the whole thing from scratch to get! >> the objects to link against.    >>  A >> Not really clear in my limited docs with the exe and olb kits.  >> Sorry about that.   >>  D >> The source kit from haxx.se has all the changes I made to make itB >> (reasonably) VMS savvy folded into the distribution.  Building E >> the whole VMS obj, olb and exe is pretty easy, but time consuming.  >>  B >> The .exe* files in the downloadable zip file from haxx.se is a E >> standalone cURL executable that you can use from the command line. C >> After defining the foreign command or path, of course.  The olb* C >> files are useful only if you write c code (or any compatible HP  3 >> VMS language, I suppose) to call cURL functions.  >>  C >> I guess I should include some sample apps in the [.packages.vms] C >> subdirectory of the source tree with some documentation.  I'm a  C >> version behind in the dist already, so maybe I can add that for   >> the 7.15.4 version. > B > FWIW I have been busy re-organising the latest cURL distributionB > to support a PCSI build. The current PCSI kit that has been made, > available is not as great as I would like.  * There is a PCSI kit for cURL?  News to me.  B > I'm not sure what I'll do about rolling it into the general cURL > distribution as yet.   Ask Daniel for CVS access.  H > I have shuffled most of the VMS stuff around and added TECO macros and@ > DCL to generate some VMS specific bits and pieces. Not sure on( > a release date, but it should be soon.  = Most of the VMS stuff was in the [.packages.vms] directory, I A thought.  The various bits get copied to their target directories = if they are different.  What VMS stuff were you referring to?   A > There also seems to be some problems related to SSL and cURL on * > VMS that I'm trying to sort out as well.  @ Haven't seen any reports on the cURL-library mailing list.  What are the problems?    Regards, Marty    ------------------------------  # Date: Mon, 19 Jun 2006 17:26:05 GMT  From: hoff@hp.nospam () 3 Subject: Re: create and modify user, but not delete 1 Message-ID: <N6Blg.2041$EN4.639@news.cpqcorp.net>   ] In article <1150404589.904150.165380@y41g2000cwy.googlegroups.com>, mabbuttg@yahoo.ca writes: J |> We have a need for one of our operators to be able to create and modifyF |> user accounts, but we want to prevent him from being able to delete |> them.  G   An operator can cause as much damage through modifications as through G   outright deletion -- outright deletion of a user entry does also have :   the general advantage of being rather more obvious, too.  I |> For the moment he has full rights across the board, which I'm not very 9 |> comfortable with, but occasionally there is some queue F |> management/creation/deletion/manipulation of jobs we get him to do.  C   The usual approach is via a captive command procedure, or through E   DCL-based CGI and a web server, or such; through an interface that  B   provides the appropriate access and that blocks untoward access.D   (And you have to be careful to avoid opening a security hole here,
   of course.)   J |> What can I set up either in system priveleges or inside of AUTHORIZE to$ |> restrict him from deleting users?  C   OpenVMS takes the all-or-nothing view toward any of the ALL-class D   privileges -- once you can write to the SYSUAF via AUTHORIZE, you E   can write to SYSUAF.  (Where SYSUAF based on a relational database, E   you might well see the ability to protect records, but it's not...)   D   I might well enable security audits for the authorization databaseD   regardless, and consider leaving the operator alone -- the audits E   will tell you what was modified, by whom, and when.  If you are not E   able to trust the operator, then you need to rethink the permitted  D   access, and may well want to cut him back to, say, TMPMBX, NETMBX F   and OPER.  Any of the ALL-class privileges can cause serious damage -   to system stability and up-time, obviously.    ------------------------------    Date: 19 Jun 2006 07:57:42 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) . Subject: Re: How can I read a locked VMS file?3 Message-ID: <DhXjUHlpHGxJ@eisner.encompasserve.org>   c In article <vu2dnXURG58ZfQ_ZnZ2dnUVZ_q6dnZ2d@libcom.com>, Dave Froble <davef@tsoft-inc.com> writes:  > ; > The BACKUP >>should<< pick up all allocated disk storage.   A    BACKUP honors the last used block field.  Always has.  Someone ?    with a competing product pointed to a Files-11 document that ?    described this as a user-defined field.  RMS always sets it. C    The disk XQP/ACP documentation in the I/O User's Guide describes     it accurately.   E    It is possible to use the $QIO interface to put data in a file and =    not set the last used block field, but I've only known one D    application that did this, and the effect was the same as markingD    the file /nobackup, which was the correct way to handle that file
    anyhow.   ------------------------------    Date: 19 Jun 2006 07:58:47 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) . Subject: Re: How can I read a locked VMS file?3 Message-ID: <fuOlee95$ZSS@eisner.encompasserve.org>   p In article <lNadnagl2MWrhQ7ZnZ2dnUVZ_tednZ2d@comcast.com>, "Richard B. Gilbert" <rgilbert88@comcast.net> writes: > G > I hearby retract foolish remarks I've made in the past about VMS/RMS  G > writing things to disk.  It appears that VMS, at least, V7.2-1 is no  H > better than Unix about actually committing things to disk and that if K > I'd lost power before closing the file the contents would have been lost.   G    VMS gives the user control over the buffering of the file.  It never +    has made it impossible to buffer a file.    ------------------------------  # Date: Mon, 19 Jun 2006 07:08:23 GMT L From: winston@SSRL.SLAC.STANFORD.EDU (Alan Winston - SSRL Central Computing)9 Subject: Re: Just Ask The Vendor: Can OpenVMS Scale Down? 6 Message-ID: <00A576BC.F164BC50@SSRL.SLAC.STANFORD.EDU>  c In article <S_WdnSISzYYesgvZnZ2dnUVZ_oadnZ2d@libcom.com>, Dave Froble <davef@tsoft-inc.com> writes:  >JF Mezei wrote: >> Karsten Nyblad wrote:H >>> manufactures as examples.  Boeing is using Baan because that companyL >>> specializes in ERP for manufactures of highly complex products.  You areH >>> a bad manager if you buy an ERP system without checking that the ERP% >>> system can support his company.    >>  E >> I know that SAP was suggested by upper manament at the 3rd largest E >> aircraft manufacturer, and the people below had to spend much time D >> convincing upper management that it would be a very wrong choice. >>  ) >>>  Only so many companies have business I >>> processes as there key competence.  Perhaps the rest of the companies / >>> should be ready to take advice from others.  >>  K >> Well, lets look at the PC industry. When it comes to commodity products, H >> business process is what differentiates yourself from competitors andI >> what allows you to be better (or worse) than your competitor. And Dell K >> has a big edge over HP because its business processes are more efficient 3 >> with fewer middlemen (distributors) in the way.   > L >At least one person feels that better prices on CPUs is the Dell advantage.  M I've read elsewhere that the Dell advantage on their systems using the "build J to order" approach combined with JIT component delivery is that they have L the customer money in hand immediately and get to pay their suppliers net 30O days; this gets them free use of the money for that time, and you can do pretty 1 well with wads of loose cash in the money market.   2 That would be all business practices, wouldn't it?   -- Alan    ------------------------------    Date: 19 Jun 2006 08:05:45 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 9 Subject: Re: Just Ask The Vendor: Can OpenVMS Scale Down? 3 Message-ID: <wTPn$WxvLw41@eisner.encompasserve.org>   p In article <neOdndp-npPThw7ZnZ2dnUVZ_rednZ2d@comcast.com>, "Richard B. Gilbert" <rgilbert88@comcast.net> writes: > A > A few years ago, I installed a Java Development Kit on VMS.  I  E > downloaded a bunch of stuff from somewhere on SUN.COM and followed  J > directions.  The developers who requested it were apparently happy with K > it.  I think it was JDK 1.2 but I won't swear to it.  Don't know if it's  , > still available.  Have you looked for one? >   C    I have the JDK on all my Alphas.  We use VMS as our primary Java A    development platform, then ship the .class files to VMS, IRIX, %    Mac, Solaris, and Windows systems.   D    The only problem I had was a decision to freeze the Windos JRE atC    an older version that didn't include some of the classes I found 	    handy.    ------------------------------    Date: 19 Jun 2006 08:08:09 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) 9 Subject: Re: Just Ask The Vendor: Can OpenVMS Scale Down? 3 Message-ID: <2co9qDj9DRoD@eisner.encompasserve.org>   c In article <ELKdnVR1zLP8Dg7ZnZ2dnUVZ_qidnZ2d@libcom.com>, Dave Froble <davef@tsoft-inc.com> writes:  > K > The ISV has concerns about finding new people to work with the software.  I >   My response was, "Don't look for people who know VMS and Basic.  I'm  J > sure they are out there.  You'd be better off finding 'good' people and E > training them on your system.  You'll have to train regardless, so  G > learning VMS and Basic is just a bit more training.  Good people can  = > learn."  I also mentioned the HP web site and job listings.   C    Your ISV is heading down the wrong, but commonly traveled, path.   F    The whole reason we bought all those VAXen in the '80s was that VMS    was so easy to learn.  H    We look for application knowledge, and avoid programers who only know)    one OS.  That's all we've ever needed.    ------------------------------    Date: 19 Jun 2006 08:12:17 -0500; From: koehler@eisner.nospam.encompasserve.org (Bob Koehler) , Subject: Re: Open VMS OS recovery on Itanium3 Message-ID: <$wKaqah5oDon@eisner.encompasserve.org>   f In article <FYDkg.2009$dA1.1419@news.cpqcorp.net>, Keith Parris <keithparris_NOSPAM@yahoo.com> writes: > I > But most users will never have to deal with that. Upon delivery, a new  D > Integrity box with OpenVMS already has the correct console serial : > input/output devices set up, and it auto-boots into the J > factory-installed OpenVMS software, which acts just like the FIS you've ; > been used to on Alpha, or like the Alpha installation CD.   G    I've never been one of those users.  I'm the kind of guy who editted G    DEBOO.CMD on his 11/780 to insert a small VAX program that had to be A    loaded in HEX because DEC's memory controller didn't recognise      National Semiconductor's RAM.   ------------------------------    Date: 19 Jun 2006 11:24:30 -05004 From: kuhrt.nospammy@encompasserve.org (Marty Kuhrt)/ Subject: Re: Problem with "New mail" broadcasts 3 Message-ID: <rEtZBsedItad@eisner.encompasserve.org>   ` In article <ADChg.1609$Ot2.676@news.cpqcorp.net>, Hoff Hoffman <hoff-remove-this@hp.com> writes: > Farrell, Michael wrote: H >> " You could, additionally, use a chunk of code to interrogate the new( >> mail count every once in a while ..." >>   >> How does one do that? > E >    Through the MAILCOUNT tool or some such, on a Freeware circa V4.  > 7 >    Or using the callable MAIL API from your own code.  > J >    The MAIL API is documented in the utility routines reference manual, ( > part of the OpenVMS documentation set.    9 This can be done in DCL as well.  Here is a chunk of code 8 I got from somewhere that checks the newmail count for a5 bunch of accounts.  Adjust to your environment, YMMV.   
 $ set noon $ byte_offset = %X23' $ user_list = "ACCT1,ACCT2,ACCT3,ACCT4"  $ count = 0 " $ vmsmail_data = "VMSMAIL_PROFILE"' $ open/read/write/share=write vmsmail - /      'f$parse(vmsmail_data,"SYS$SYSTEM:.DATA")'  $loop:/ $ user_name = f$element( count, ",", user_list) ( $ if user_name .eqs. "," then goto finis7 $ read/error=no_user vmsmail record /key="''user_name'" 1 $ num_message = f$cvsi(byte_offset*8, 16, record) ; $ message = f$fao("User !AS has !SL new mail message!%S", - >                    f$edit(user_name, "COLLAPSE"), num_message) $ write sys$output message $ count = count + 1  $ goto loop 	 $no_user: - $ write sys$output "No such user ", user_name  $ count = count + 1  $ goto loop  $finis:  $ close vmsmail  $ exit   ------------------------------    Date: 19 Jun 2006 05:12:49 -0700$ From: "AEF" <spamsink2001@yahoo.com>R Subject: Re: Q: (long) DCL symbols not appearing in Show Symbol output [SLS V2.9H]B Message-ID: <1150719169.747005.284640@r2g2000cwb.googlegroups.com>   Ken Fairfield wrote:C > Having worked with VMS for more than 20 years, I really thought I ? > understood DCL.  But here's a puzzle I just can't understand!  > @ > In the context of SLS's POST_PROCESS_EACH.COM (and similar forH > PRE_PROCESS_FIRST, PRE_PROCESS_EACH and POST_PROCESS_LAST, SLS V2.9H),J > I was trying to determine what *symbols* are available to that procedureH > (since the documentation in Section 5.3.3.1 & 5.3.3.2 of the "Guide toE > Backup and Restore Operations" is known to be incorrect).  Near the : > beginning of my procedure, I inserted the following DCL: >  > E > $Write Sys$Output "''F$Fao("!30*% In POST_PROCESS_EACH !30*%!/ ")'"  > $ Show Symbol *  > $ Show Symbol /Local  *  > $ Show Symbol /Global *  > $ Show Symbol /Local  status > $ Show Symbol /Global status! > $ Show Symbol /Local  statusmsg ! > $ Show Symbol /Global statusmsg  > $ Show Symbol first_reel > $ Show Symbol last_reel  > $ Show Symbol first  > $ Show Symbol last > $ Show Symbol status > $ Show Symbol statusmsg E > $Write Sys$Output "''F$Fao("!/ !30*% In POST_PROCESS_EACH !30*%")'"  >  > C > There's a lot of redundancy here as I was trying "many" different F > approaches.  Note that the documentation claims that all of 'first',G > 'last', 'status' and 'statusmsg', are supposed to be available to all I > four procedures.  'first_reel' and 'last_reel' are *not* documented but / > are, in fact, available in POST_PROCESS_EACH.  > H > I discovered three things that I cannot explain (see the output at the > bottom of this post):  > E >     1) *Neither* 'first_reel' nor 'last_reel' are present in any of B >        the wildcard Show Symbol commands.  They are present on a6 >        Show Symbol of those names.  How can that be? > C >     2) 'status' is not present on any of the wildcard Show Symbol D >        commands, nor on "Show Symbol [ /Local | /Global ] status".E >        However, the local symbol 'status' is present (see output of C >        the next to last Show Symbol command below).  How can that 
 >        be??  > F >     3) 'statusmsg' does not appear in *any* Show Symbol output, evenB >        the last.  However, it is present. For example, I can do: > ; >          $ Write Sys$Output "Final status = ''statusmsg'"  > E >        and have, e.g, "Final status = BACKUP-W-ACCONFLICT," written H >        to the log file, and this after testing $ If statusmsg.Nes."" . >        How can this be???  > C > I have tried to reproduce some of these effects interactively, by G > defining local and global symbols of the same name but with different I > values, and by varying "symbol assign (:=)" versus "string assign (=)", 9 > but nothing unexpected, nothing like the above, occurs.  > F > Can anyone explain what is happening?  Is there a 3rd, or 4th, classA > of symbols I've never heard of that are hidden (sometimes) from % > Show Symbol??  Have I gone crazy???  >  >     Regards, Ken [...]    SHOW     SYMBOL       /ALL  B        Displays the current values of all symbols in the specified@        symbol table (/LOCAL or /GLOBAL). If you specify the /ALLD        qualifier and do not specify either the /LOCAL or the /GLOBALF        qualifier, the SHOW SYMBOL command displays the contents of the8        local symbol table for the current command level.       SHOW SYMBOL Subtopic?  SHOW     SYMBOL  
     /LOCAL  C        Searches only the local symbol table for the current command C        level for the specified symbol name. If you specify both the  /ALLE        and /LOCAL qualifiers, all names in the local symbol table for /        the current command level are displayed.        SHOW SYMBOL Subtopic?   5 This could explain 1 and 2. Not sure about 3, though.    ------------------------------  % Date: Mon, 19 Jun 2006 09:14:54 -0700 ( From: Jeff Cameron <roktsci@comcast.net>Y Subject: Re: Q: (long) DCL symbols not appearing in Show Symbol output [SLS V2.9H] [SLS V 0 Message-ID: <C0BC1B8E.21A49%roktsci@comcast.net>  B Since an asterisk (*) can be used within a symbol name to identifyH abbreviation, the use of an asterisk in the SHOW SYMBOL command does notF denote a wildcard for all symbols. The /ALL qualifier is used instead.   Example:  $ $ EXT*RACT == "<equivalence-string>"  D Indicates that EXT, EXTR EXTRA EXTRAC and EXTRACT can all be used to identify the symbol.   Jeff  B On 6/16/06 3:32 PM, in article e6vbik$7m6$2@news01.intel.com, "Ken* Fairfield" <my.full.name@intel.com> wrote:  C > Having worked with VMS for more than 20 years, I really thought I ? > understood DCL.  But here's a puzzle I just can't understand!  > @ > In the context of SLS's POST_PROCESS_EACH.COM (and similar forH > PRE_PROCESS_FIRST, PRE_PROCESS_EACH and POST_PROCESS_LAST, SLS V2.9H),J > I was trying to determine what *symbols* are available to that procedureH > (since the documentation in Section 5.3.3.1 & 5.3.3.2 of the "Guide toE > Backup and Restore Operations" is known to be incorrect).  Near the : > beginning of my procedure, I inserted the following DCL: >  > E > $Write Sys$Output "''F$Fao("!30*% In POST_PROCESS_EACH !30*%!/ ")'"  > $ Show Symbol *  > $ Show Symbol /Local  *  > $ Show Symbol /Global *  > $ Show Symbol /Local  status > $ Show Symbol /Global status! > $ Show Symbol /Local  statusmsg ! > $ Show Symbol /Global statusmsg  > $ Show Symbol first_reel > $ Show Symbol last_reel  > $ Show Symbol first  > $ Show Symbol last > $ Show Symbol status > $ Show Symbol statusmsg E > $Write Sys$Output "''F$Fao("!/ !30*% In POST_PROCESS_EACH !30*%")'"  >  > C > There's a lot of redundancy here as I was trying "many" different F > approaches.  Note that the documentation claims that all of 'first',G > 'last', 'status' and 'statusmsg', are supposed to be available to all I > four procedures.  'first_reel' and 'last_reel' are *not* documented but / > are, in fact, available in POST_PROCESS_EACH.  > H > I discovered three things that I cannot explain (see the output at the > bottom of this post):  > E >     1) *Neither* 'first_reel' nor 'last_reel' are present in any of B >        the wildcard Show Symbol commands.  They are present on a6 >        Show Symbol of those names.  How can that be? > C >     2) 'status' is not present on any of the wildcard Show Symbol D >        commands, nor on "Show Symbol [ /Local | /Global ] status".E >        However, the local symbol 'status' is present (see output of C >        the next to last Show Symbol command below).  How can that 
 >        be??  > F >     3) 'statusmsg' does not appear in *any* Show Symbol output, evenB >        the last.  However, it is present. For example, I can do: > ; >          $ Write Sys$Output "Final status = ''statusmsg'"  > E >        and have, e.g, "Final status = BACKUP-W-ACCONFLICT," written H >        to the log file, and this after testing $ If statusmsg.Nes."" . >        How can this be???  > C > I have tried to reproduce some of these effects interactively, by G > defining local and global symbols of the same name but with different I > values, and by varying "symbol assign (:=)" versus "string assign (=)", 9 > but nothing unexpected, nothing like the above, occurs.  > F > Can anyone explain what is happening?  Is there a 3rd, or 4th, classA > of symbols I've never heard of that are hidden (sometimes) from % > Show Symbol??  Have I gone crazy???  >  >     Regards, Ken > P > ==============================================================================H > $Write Sys$Output "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH > %%%%%%%%%  > %%%%%%%%%%%%%%%%%%%%%  >   " 5 > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH  > %%%%%%%%%%%%%%%%%%%%%%%%%%%% > %% >  > $ Show Symbol *  >    $RESTART == "FALSE" >    $SEVERITY == "1"  >    $STATUS == "%X00010001"7 >    AUTOSEL == 1   Hex = 00000001  Octal = 00000000001  >    BACKUP_TYPE == "VMSBACKUP"  >    BTYPE = "WEEKLY_DAY5" >    BUTYPE == "Weekly" ) >    CONTINUE == "RA2SW_WW24_2006_WEEKLY" ; >    CONTLOADOPT == 2   Hex = 00000002  Octal = 00000000002  >    DB_FILE_QUALS == ""8 >    DC$_TAPE == 2   Hex = 00000002  Octal = 00000000002 >    DENSITY == "COMP" >    DEVICE = "WS$SDISK:"  >    DRIVE_TYPE == "" 6 >    END_TM == 0   Hex = 00000000  Octal = 00000000000 >    FILES_1 == "WS$SDISK" >    FILES_2 == "WS$S2DISK"  >    FILES_3 == "WS_LOGS"  >    FILES_4 == "DOSD_DUMP366" >    FILES_5 == "DOSD_DUMP367" >    FULL == "0" >    HISTORY_SET == "IMAGE" 8 >    IGNBLANK == 0   Hex = 00000000  Octal = 00000000000 >    LCS_WW == "200624"  >    LISTING_GEN == "" >    LOG_FILE == "/NOPRINT" C >    MAIL_FILE = "SLS$SYSBAK:RA2SW_WEEKLY_DAY5_BACKUP_21894C6D.SUM"  >    MEDIA_TYPE == "TZ89" @ >    MNT$M_MESSAGE == 8192   Hex = 00002000  Octal = 00000020000B >    MNT$M_READCHECK == 2048   Hex = 00000800  Octal = 00000004000K >    MNT$M_TAPE_DATA_WRITE == 2097152   Hex = 00200000  Octal = 00010000000 D >    MNT$M_WRITECHECK == 32768   Hex = 00008000  Octal = 00000100000> >    MNTFLAGS == 2105344   Hex = 00202000  Octal = 00010020000 >    NEXT_JOB == "" 4 >    NOTES == "RA2SW Weekly Image Backups WW24 2006"8 >    N_DRIVES == 1   Hex = 00000001  Octal = 00000000001 >    OFFSITE_DATE == ""  >    ONSITE_DATE == ""! >    P1 = "RA2SW_WEEKLY_DAY5_SBK" 
 >    P2 = "1"  >    P3 = "WS$SDISK:"  >    P4 = "" >    P5 = "" >    P6 = "" >    P7 = "" >    P8 = ""& >    PARAMS == "RA2SW_WEEKLY_DAY5_SBK"= >    POST_PROCESS_EACH == "@SLS$SYSBAK:POST_PROCESS_EACH.COM" = >    POST_PROCESS_LAST == "@SLS$SYSBAK:POST_PROCESS_LAST.COM" 8 >    PREALLOC == 0   Hex = 00000000  Octal = 00000000000 >    PRE_PROCESS_EACH == "!"= >    PRE_PROCESS_FIRST == "@SLS$SYSBAK:PRE_PROCESS_FIRST.COM"  >    PRINT_Q == "SYS$PRINT"  >    PRIVS == "BYPASS"8 >    PROGRESS == 0   Hex = 00000000  Octal = 00000000000& >    PROTECTION == "S:RW,O:RW,G:R,W:R"> >    QUALIFIERS == "/RECO/IMAGE/NOALIAS/IGNO=INTE/BLOCK=65534"9 >    QUICKLOAD == 1   Hex = 00000001  Octal = 00000000001 C >    QUICKLOAD_RETRIES == 360   Hex = 00000168  Octal = 00000000550 * >    REDIRECT_OPCOM == "RA2SBS::$3$MKF200"; >    REEL_SIZE == 857   Hex = 00000359  Octal = 00000001531 & >    REPLY_MSG == "REQUEST/TO=(TAPES)"@ >    SAVESET_GEN == "F$EXTRACT(0,17,DO_DISK) + ".BAK" - "DISK$""9 >    SBK_FILES == 5   Hex = 00000005  Octal = 00000000005 # >    SBK_NAME = "RA2SW_WEEKLY_DAY5" - >    SBK_STARTED == "16-JUN-2006 00:35:08.81"  >    SBK_VOLUMES == "VS0194" >    SBUPDT_Q == "SLS$SW_TAPE"= >    SCRATCH_DAYS == 40   Hex = 00000028  Octal = 00000000050  >    SEVERITY_LEVEL == "F"= >    SS$_BADPARAM == 20   Hex = 00000014  Octal = 00000000024 ? >    SS$_DEVALLOC == 2112   Hex = 00000840  Octal = 00000004100 > >    SS$_DEVMOUNT == 108   Hex = 0000006C  Octal = 00000000154? >    SS$_NODEVAVL == 2480   Hex = 000009B0  Octal = 00000004660 < >    SS$_REJECT == 660   Hex = 00000294  Octal = 00000001224 >    START_TM == "75"  >    STATUS_MAIL == ""< >    SUMMARY_FILE == 2   Hex = 00000002  Octal = 00000000002: >    TAPE_COUNT == 1   Hex = 00000001  Octal = 00000000001; >    TAPE_LABELS == 0   Hex = 00000000  Octal = 00000000000  >    TAPE_POOL == ""B >    UNATTENDED_BACKUPS == 1   Hex = 00000001  Octal = 00000000001 >    WORKWEEK == "24"  >    WORKWEEK_Q == "Q2"  > $ Show Symbol /Local  *  >    BTYPE = "WEEKLY_DAY5" >    DEVICE = "WS$SDISK:" C >    MAIL_FILE = "SLS$SYSBAK:RA2SW_WEEKLY_DAY5_BACKUP_21894C6D.SUM" ! >    P1 = "RA2SW_WEEKLY_DAY5_SBK" 
 >    P2 = "1"  >    P3 = "WS$SDISK:"  >    P4 = "" >    P5 = "" >    P6 = "" >    P7 = "" >    P8 = ""# >    SBK_NAME = "RA2SW_WEEKLY_DAY5"  > $ Show Symbol /Global *  >    $RESTART == "FALSE" >    $SEVERITY == "1"  >    $STATUS == "%X00010001"7 >    AUTOSEL == 1   Hex = 00000001  Octal = 00000000001  >    BACKUP_TYPE == "VMSBACKUP"  >    BUTYPE == "Weekly" ) >    CONTINUE == "RA2SW_WW24_2006_WEEKLY" ; >    CONTLOADOPT == 2   Hex = 00000002  Octal = 00000000002  >    DB_FILE_QUALS == ""8 >    DC$_TAPE == 2   Hex = 00000002  Octal = 00000000002 >    DENSITY == "COMP" >    DRIVE_TYPE == "" 6 >    END_TM == 0   Hex = 00000000  Octal = 00000000000 >    FILES_1 == "WS$SDISK" >    FILES_2 == "WS$S2DISK"  >    FILES_3 == "WS_LOGS"  >    FILES_4 == "DOSD_DUMP366" >    FILES_5 == "DOSD_DUMP367" >    FULL == "0" >    HISTORY_SET == "IMAGE" 8 >    IGNBLANK == 0   Hex = 00000000  Octal = 00000000000 >    LCS_WW == "200624"  >    LISTING_GEN == "" >    LOG_FILE == "/NOPRINT"  >    MEDIA_TYPE == "TZ89" @ >    MNT$M_MESSAGE == 8192   Hex = 00002000  Octal = 00000020000B >    MNT$M_READCHECK == 2048   Hex = 00000800  Octal = 00000004000K >    MNT$M_TAPE_DATA_WRITE == 2097152   Hex = 00200000  Octal = 00010000000 D >    MNT$M_WRITECHECK == 32768   Hex = 00008000  Octal = 00000100000> >    MNTFLAGS == 2105344   Hex = 00202000  Octal = 00010020000 >    NEXT_JOB == "" 4 >    NOTES == "RA2SW Weekly Image Backups WW24 2006"8 >    N_DRIVES == 1   Hex = 00000001  Octal = 00000000001 >    OFFSITE_DATE == ""  >    ONSITE_DATE == ""& >    PARAMS == "RA2SW_WEEKLY_DAY5_SBK"= >    POST_PROCESS_EACH == "@SLS$SYSBAK:POST_PROCESS_EACH.COM" = >    POST_PROCESS_LAST == "@SLS$SYSBAK:POST_PROCESS_LAST.COM" 8 >    PREALLOC == 0   Hex = 00000000  Octal = 00000000000 >    PRE_PROCESS_EACH == "!"= >    PRE_PROCESS_FIRST == "@SLS$SYSBAK:PRE_PROCESS_FIRST.COM"  >    PRINT_Q == "SYS$PRINT"  >    PRIVS == "BYPASS"8 >    PROGRESS == 0   Hex = 00000000  Octal = 00000000000& >    PROTECTION == "S:RW,O:RW,G:R,W:R"> >    QUALIFIERS == "/RECO/IMAGE/NOALIAS/IGNO=INTE/BLOCK=65534"9 >    QUICKLOAD == 1   Hex = 00000001  Octal = 00000000001 C >    QUICKLOAD_RETRIES == 360   Hex = 00000168  Octal = 00000000550 * >    REDIRECT_OPCOM == "RA2SBS::$3$MKF200"; >    REEL_SIZE == 857   Hex = 00000359  Octal = 00000001531 & >    REPLY_MSG == "REQUEST/TO=(TAPES)"@ >    SAVESET_GEN == "F$EXTRACT(0,17,DO_DISK) + ".BAK" - "DISK$""9 >    SBK_FILES == 5   Hex = 00000005  Octal = 00000000005 - >    SBK_STARTED == "16-JUN-2006 00:35:08.81"  >    SBK_VOLUMES == "VS0194" >    SBUPDT_Q == "SLS$SW_TAPE"= >    SCRATCH_DAYS == 40   Hex = 00000028  Octal = 00000000050  >    SEVERITY_LEVEL == "F"= >    SS$_BADPARAM == 20   Hex = 00000014  Octal = 00000000024 ? >    SS$_DEVALLOC == 2112   Hex = 00000840  Octal = 00000004100 > >    SS$_DEVMOUNT == 108   Hex = 0000006C  Octal = 00000000154? >    SS$_NODEVAVL == 2480   Hex = 000009B0  Octal = 00000004660 < >    SS$_REJECT == 660   Hex = 00000294  Octal = 00000001224 >    START_TM == "75"  >    STATUS_MAIL == ""< >    SUMMARY_FILE == 2   Hex = 00000002  Octal = 00000000002: >    TAPE_COUNT == 1   Hex = 00000001  Octal = 00000000001; >    TAPE_LABELS == 0   Hex = 00000000  Octal = 00000000000  >    TAPE_POOL == ""B >    UNATTENDED_BACKUPS == 1   Hex = 00000001  Octal = 00000000001 >    WORKWEEK == "24"  >    WORKWEEK_Q == "Q2"  > $ Show Symbol /Local  status? > %DCL-W-UNDSYM, undefined symbol - check validity and spelling  > $ Show Symbol /Global status? > %DCL-W-UNDSYM, undefined symbol - check validity and spelling ! > $ Show Symbol /Local  statusmsg ? > %DCL-W-UNDSYM, undefined symbol - check validity and spelling ! > $ Show Symbol /Global statusmsg ? > %DCL-W-UNDSYM, undefined symbol - check validity and spelling  > $ Show Symbol first_reel >    FIRST_REEL = "VS0194" > $ Show Symbol last_reel  >    LAST_REEL = "VS0194"  > $ Show Symbol first ? > %DCL-W-UNDSYM, undefined symbol - check validity and spelling  > $ Show Symbol last? > %DCL-W-UNDSYM, undefined symbol - check validity and spelling  > $ Show Symbol status >    STATUS = "%X10A38410" > $ Show Symbol statusmsg ? > %DCL-W-UNDSYM, undefined symbol - check validity and spelling  > $Write Sys$Output " 7 >   %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH  > %%%%%%%%%%%%%%%%%%%%%%%%%%%  > %%%" > 7 >   %%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In POST_PROCESS_EACH  > %%%%%%%%%%%%%%%%%%%%%%%%%%%  > %%% P > ==============================================================================   ------------------------------  + Date: Mon, 19 Jun 2006 10:23:19 +0000 (UTC)  From: david20@alpha2.mdx.ac.uk- Subject: Re: Sending HTML mail from VMS MAIL? ) Message-ID: <e75tun$8mr$2@news.mdx.ac.uk>   \ In article <4492FDE8.54BDB935@teksavvy.com>, JF Mezei <jfmezei.spamnot@teksavvy.com> writes: >Syltrem wrote:  >> > $ cr[0,8]=13  >> > $ lf[0,8]=10 : >> > $ subject="[BACKUP] VMS Backup Summary" + cr + lf + -5 >> >                "Mime-Version: 1.0" + cr + lf + - - >> >                "Content-Type: text/HTML" 7 >> > $ mail/sub="''subject'" 'summary_file support_dist  >  >  >> That works great !  >  > H >It may work today, but I am not sure this is garanteed to work forever.  N Hopefully the reason it would break in the future is that somebody has decidedH to do enough work on VMS Mail to allow it to natively support MIME (in a similar manner to PMDF MAIL).   
 David Webb Security team leader CCSS Middlesex University   ------------------------------   End of INFO-VAX 2006.339 ************************                                                                                                                                                                                    ux "/2]_Ϸ P/
=m605FV(<ˍ^]U!%$(\jG@ƸPzV'%cuQ2#D؜gspYM*TUS-5EĠWNB'd(*#bVD^|bR2҇F7}36-{$ʬX4ϐ/
oK-ngLJB});JЍ<v ~{}+& B!3Ve,Nas?f2[:Qǰ9n
3)(~Kckpzj߼y-MX/7^z{Ľt0l(){)*h?ڧ;^
gMuM~)`D]3MPܚg
!Bx ʱXj}UԀ6,$ŹX3r(_(rBEEGp}
I[٥<n*[\e\U[*Y9I=Tn+P+6؂1T5*dhK!2dƇtBjax7z`tr5z"ّ#		g. rxy<,ȆǩE,Zhm
hxL+,Ã5?	!uՊefb
ybf-]zdV5*uuw^;T	-
1[t\bXBCG`	j5a
TPvAUd՞ģNT-[xﬓC\H
],&KTTomlDO0@ <&p+6x"dl6tA{[2?}(#tY_F-dpL]az>AJ>2zs/1=e`~8<xh>cA0h<KUm~mDtޤ.89{>d@e9H$HGmLFӮH3Nx}ƴתzs_ZDC G;/v'{1\ 1,|6CΊG1
J
nt
=~dtqfA3wE6Iי֟JnJlG$qg҃mFyWLjt81[i9_,W/MFuVzo
NO99~uDcB94jJ̽qi陥Oax9,qDqM.Wo=l&!33`#h^T7rCz&gޓMQaG7)S%+$ !bNZjjDh7'5iVDZ)ySi17GbKL3@j\qU @
$]:⟭?s!JƙZKj5%fN9_S15vzlaec^tV
=]{{2cJS&[O
˧ %;ymݧX|Cu+fMf0I1zS8C}]YPG;7ቯv4Za