INFO-VAX Mon, 14 Jan 2008 Volume 2008 : Issue 27 Contents: Re: Anyway to "smarten up" the console terminal? Re: Changing passwords Re: Changing passwords Re: F$UNIQUE library function Re: F$UNIQUE library function Re: F$UNIQUE library function Re: F$UNIQUE library function Re: IA64 VMS installation DVD creation. Re: IA64 VMS installation DVD creation. Re: IA64 VMS installation DVD creation. Re: OT - EISNER:: upgrade complete Re: print queues and IP ---------------------------------------------------------------------- Date: Sun, 13 Jan 2008 19:44:26 -0600 From: Slor Subject: Re: Anyway to "smarten up" the console terminal? Message-ID: Despite all prevention efforts, "FredK" wrote in news:fmdae6$tn8$1@usenet01.boi.hp.com: > Seriously? You want someone (me) to enhance the console code for a > DEC3000? Well, not asking anyone to anhance anything - just looking for definitive information on what can currently be done. > The graphics on this predate those with VGA text mode. The code lives > in a device driver that does it's own bitmapped text. It is pretty > much what you got with a VAXstation 1. The intent of the graphics > based console was to provide the minimum needed to allow limited > console interaction. > > I "threw in" a simple VT52 emulation when I did the VGA text mode > logic that at least allows EDIT/EDT to work for the most part. It > probably also works on the last generation of the TGA without VGA text > mode... but I do not believe I even attempted to retrofit it to the > TurboChannel based systems. That pretty much answers my questions. Thanks for the insights and the quick stroll down memory lane. :) -- James http://www.e-host-direct.com Reliable web hosting from $12/year. ------------------------------ Date: Sun, 13 Jan 2008 20:21:53 +0100 From: "P. Sture" Subject: Re: Changing passwords Message-ID: In article <15e981b4-6ecc-492e-954a-3ab921ed1402@v67g2000hse.googlegroups.com>, H Vlems wrote: > On 13 jan, 17:14, rtk wrote: > > On Jan 13, 8:38 am, Bob Gezelter wrote: > > > > > > > > > You will find the documentation of this online, within the AUTHORIZE > > > utility, by entering HELP MODIFY /PWDLIFETIME (/NOPWDLIFETIME or / > > > PWDLIFETIME=NONE disables password expiration). > > > > Bob, this appears to have worked, thank you.  Do you know how to clear > > the password history file so I can set my, hopefully final, password > > to the one I want? > > > > Ron > > Use AUTHORIZE, that way you'll bypass the history file. > Hans AUTHORIZE will by default set the password to expired if you change it there, so: UAF> modify myusername /password=whatever /nopwdexpired -- Paul Sture Sue's OpenVMS bookmarks: http://eisner.encompasserve.org/~sture/ovms-bookmarks.html ------------------------------ Date: Sun, 13 Jan 2008 12:23:00 -0800 (PST) From: Bob Gezelter Subject: Re: Changing passwords Message-ID: <2fe5e7c5-7428-4e31-8d67-b32fcf35401c@c23g2000hsa.googlegroups.com> On Jan 13, 11:14 am, rtk wrote: > On Jan 13, 8:38 am, Bob Gezelter wrote: > > > > > You will find the documentation of this online, within the AUTHORIZE > > utility, by entering HELP MODIFY /PWDLIFETIME (/NOPWDLIFETIME or / > > PWDLIFETIME=NONE disables password expiration). > > Bob, this appears to have worked, thank you. Do you know how to clear > the password history file so I can set my, hopefully final, password > to the one I want? > > Ron Ron, In AUTHORIZE, one can disable password history checking on an account by account basis using the /FLAG=DISPWDHIS on the MODIFY command (see the appropriate HELP text). On a global basis, one can control this on a system wide basis using the SYS$PASSWORD_HISTORY_LIMIT and SYS$PASSWORD_HISTORY_LIFETIME system logical names. This is documented in the OpenVMS Guide to System Security, available from the OpenVMS www site at http://www.hp.com/go/openvms - Bob Gezelter, http://www.rlgsc.com ------------------------------ Date: Sun, 13 Jan 2008 20:05:12 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: F$UNIQUE library function Message-ID: In article , yyyc186 writes: > > >Here's a little oddity. I don't find a SYS$ version of F$UNIQUE like >most of the other lexical functions have. Did HP once again breech >the tradition or did they stick it in a LIB$ function some where? SYS$CREATE_UID -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Sun, 13 Jan 2008 21:13:24 GMT From: =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= Subject: Re: F$UNIQUE library function Message-ID: VAXman- @SendSpamHere.ORG wrote: > In article , yyyc186 writes: >> >> Here's a little oddity. I don't find a SYS$ version of F$UNIQUE like >> most of the other lexical functions have. Did HP once again breech >> the tradition or did they stick it in a LIB$ function some where? > > SYS$CREATE_UID > If I understand F$UNIQUE correctly, it generates the same number (or "unique identifier") as is described here : http://en.wikipedia.org/wiki/UUID , right ? It's just the standard formatting in 8-4-4-4-12 groups that is "missing", but very easily added, of course : $ uid = f$unique() $ uuid = f$extract(0,8,uid) + "-" + - f$extract(8,4,uid) + "-" + - f$extract(12,4,uid) + "-" + - f$extract(16,4,uid) + "-" + - f$extract(20,12,uid) $ show sym *uid UID = "E235872B0008098611DCC2228494C2C5" UUID = "E235872B-0008-0986-11DC-C2228494C2C5" $ Jan-Erik ------------------------------ Date: Sun, 13 Jan 2008 21:53:48 GMT From: VAXman- @SendSpamHere.ORG Subject: Re: F$UNIQUE library function Message-ID: In article , =?ISO-8859-1?Q?Jan-Erik_S=F6derholm?= writes: > > >VAXman- @SendSpamHere.ORG wrote: >> In article , yyyc186 writes: >>> >>> Here's a little oddity. I don't find a SYS$ version of F$UNIQUE like >>> most of the other lexical functions have. Did HP once again breech >>> the tradition or did they stick it in a LIB$ function some where? >> >> SYS$CREATE_UID >> > >If I understand F$UNIQUE correctly, it generates the same >number (or "unique identifier") as is described here : >http://en.wikipedia.org/wiki/UUID , right ? > >It's just the standard formatting in 8-4-4-4-12 groups >that is "missing", but very easily added, of course : > >$ uid = f$unique() >$ uuid = f$extract(0,8,uid) + "-" + - > f$extract(8,4,uid) + "-" + - > f$extract(12,4,uid) + "-" + - > f$extract(16,4,uid) + "-" + - > f$extract(20,12,uid) >$ show sym *uid > UID = "E235872B0008098611DCC2228494C2C5" > UUID = "E235872B-0008-0986-11DC-C2228494C2C5" >$ F$unique() invokes SYS$CREATE_UID. SYS$CREATE_UID accepts a vector of 4 longwords. SYS$CREATE_UID was introduced when transaction services were incorporated into VMS. The 4 longwords (16 bytes, 128 bits) can represented by 32 hexadecimal characters. Introducing the hyphens (-) at the appropriate locations creates the familiar 36 character UUID. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM "Well my son, life is like a beanstalk, isn't it?" http://tmesis.com/drat.html ------------------------------ Date: Sun, 13 Jan 2008 22:46:37 -0500 From: "FredK" Subject: Re: F$UNIQUE library function Message-ID: Not exactly. SYS$CREATE_UID creates a valid UUID/GUID as per the standards. It returns a binary Octaword that can be directly used. However, the display or "wire" format of a UUID/GUID is broken into fields - some of which are byte-swapped. The point being, that if you see a text version of a UUID you cannot simply transpose it directly into a binary Octaword. I learned this the hard way... I believe that F$UNIQUE returns the UID by simply converting the octaword to hex - so do not just add dashes and expect ot to be a valid wire format UUID. However, the value will still be unique. // GUID tutorial: // // GUIDs are described using what is called a "wire format" which is displayed // as a combination of five fields describing a 16-byte field. The EFI partition // GUID for example is published as: // // C12A7328-F81F-11D2-BA4B-00A0C93EC93B // // To store this in memory, ignore the dashes and chop it up into 6 // fields. // // o The first 8 hex digits (32 bits) // o The next 4 hex digits (16 bits) // o The next 4 hex digits (16 bits) // o The next 4 hex digits (16 bits) // o The next 4 hex digits (16 bits) // o The next 8 hex digits (32 bits) // // 128-bits total // // Using the EFI GUID as an example, convert the fields: // // C12A7328 is stored as-is to the first uint32 // F81F is stored as-is to the next uint16 // 11D2 is stored as-is to the next uint16 // BA4B is byte-swapped (4BBA) and stored to the next uint16 // 00A0 is byte swapped (A000) and stored to the next uint16 // C93EC93B is byte swapped (3BC93EC9) and stored to the next uint32 // // Thus you can look at result as the octaword: // // 3BC93EC9A0004BBA11D2F81FC12A7328 // (high) (low) // // Which of course is a little endian byte stream of: // // 28 73 2a c1 1f f8 d2 11 ba 4b 00 a0 c9 3e c9 3b // (low) (high) // // The GUIDs stored as constants here are stored as OCTAWORDS. To // add a new GUID: // // If the GUID was supplied in xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx // format you must convert it using the scheme outlined above into // an octaword. // // If the GUID was generated by SYS$CREATE_UID -- which creates a // GUID (also known as a UUID) - then you are returned an octaword // in the correct format. // // FYI this is the definition of the EFI GUID (UUID, RFC 4122). This // matches the SYS$CREATE_UID output which we use for signatures. // // Name Offset Length Description // // TimeLow 0 4 The low field of the timestamp. // TimeMid 4 2 The middle field of the timestamp. // TimeHighAndVersion 6 2 The high field of the timestamp // multiplexed with the version number. // ClockSeqHigh 8 1 The high field of the clock sequence // multiplexed with the variant. // ClockSeqLow 9 1 The low field of the clock sequence. // Node 10 6 The spatially unique node identifier. // This can be based on any IEEE 802 // address obtained from a network card. // If no network card exists in the system, // a cryptographic-quality random number // can be used. // "Jan-Erik Söderholm" wrote in message news:U9vij.2738$R_4.1986@newsb.telia.net... > VAXman- @SendSpamHere.ORG wrote: >> In article >> , >> yyyc186 writes: >>> >>> Here's a little oddity. I don't find a SYS$ version of F$UNIQUE like >>> most of the other lexical functions have. Did HP once again breech >>> the tradition or did they stick it in a LIB$ function some where? >> >> SYS$CREATE_UID >> > > If I understand F$UNIQUE correctly, it generates the same > number (or "unique identifier") as is described here : > http://en.wikipedia.org/wiki/UUID , right ? > > It's just the standard formatting in 8-4-4-4-12 groups > that is "missing", but very easily added, of course : > > $ uid = f$unique() > $ uuid = f$extract(0,8,uid) + "-" + - > f$extract(8,4,uid) + "-" + - > f$extract(12,4,uid) + "-" + - > f$extract(16,4,uid) + "-" + - > f$extract(20,12,uid) > $ show sym *uid > UID = "E235872B0008098611DCC2228494C2C5" > UUID = "E235872B-0008-0986-11DC-C2228494C2C5" > $ > > Jan-Erik ------------------------------ Date: Sun, 13 Jan 2008 20:22:52 +0100 From: "P. Sture" Subject: Re: IA64 VMS installation DVD creation. Message-ID: In article <1arij.34009$Ux2.964@attbi_s22>, "John E. Malmberg" wrote: > P. Sture wrote: > > > > If we look at other operating systems, you can download various Linux > > and Unix variants and Solaris for PC systems. > > > > However, you cannot do that (except as an early adoptor perhaps) for > > Windows, OS X and probably quite a few others. In this regard VMS is the > > same. The only times I have acquired an early release of VMS were via a > > non-official looking tape from the local DEC/Compaq/HP office. > > If you have the appropriate level MSDN contract with Microsoft, all of > their products are available for download, both current and pre-release > versions. > > Microsoft charges more for actually shipping the CD-ROMS/DVDs. > I stand corrected. -- Paul Sture Sue's OpenVMS bookmarks: http://eisner.encompasserve.org/~sture/ovms-bookmarks.html ------------------------------ Date: Sun, 13 Jan 2008 13:14:50 -0800 (PST) From: etmsreec@yahoo.co.uk Subject: Re: IA64 VMS installation DVD creation. Message-ID: <6bfa964c-4cc5-4409-b1c4-57d37db909f1@u10g2000prn.googlegroups.com> On 13 Jan, 19:22, "P. Sture" wrote: > In article <1arij.34009$Ux2.964@attbi_s22>, > =A0"John E. Malmberg" wrote: > > > > > > > P. Sture wrote: > > > > If we look at other operating systems, you can download various Linux > > > and Unix variants and Solaris for PC systems. > > > > However, you cannot do that (except as an early adoptor perhaps) for > > > Windows, OS X and probably quite a few others. In this regard VMS is t= he > > > same. The only times I have acquired an early release of VMS were via = a > > > non-official looking tape from the local DEC/Compaq/HP office. > > > If you have the appropriate level MSDN contract with Microsoft, all of > > their products are available for download, both current and pre-release > > versions. > > > Microsoft charges more for actually shipping the CD-ROMS/DVDs. > > I stand corrected. > > -- > Paul Sture > > Sue's OpenVMS bookmarks:http://eisner.encompasserve.org/~sture/ovms-bookma= rks.html- Hide quoted text - > > - Show quoted text - Following John M's comments further up this thread, I am right in thinking that it's ok backing up an installed system disk using BACKUP/ IMAGE/NOALIAS and this will give a working disk when restored, aren't I? Steve ------------------------------ Date: Sun, 13 Jan 2008 22:28:14 -0500 From: "FredK" Subject: Re: IA64 VMS installation DVD creation. Message-ID: When BACKUP sees the file GPT.SYS (and SYS$EFI.SYS) it knows that the volume is a bootable Integrity disk. When you restore the backup it will call SETBOOT to create valid GPT.SYS boot information. So yes, a system disk can be backed up and restored and will be bootable (note that you will need to update any saved boot entry data to allow it to be automatically booted from the EFI menu). In fact, you should be able to restore a installation DVD to a disk and it should work. What you can't do is *reliably* create a bootable DVD without knowing the magic needed to create the El Torito boot information. We are looking at providing a way for a customer to do this for the handful of legitimate uses for it. wrote in message news:6bfa964c-4cc5-4409-b1c4-57d37db909f1@u10g2000prn.googlegroups.com... On 13 Jan, 19:22, "P. Sture" wrote: > In article <1arij.34009$Ux2.964@attbi_s22>, > "John E. Malmberg" wrote: > > > > > > > P. Sture wrote: > > > > If we look at other operating systems, you can download various Linux > > > and Unix variants and Solaris for PC systems. > > > > However, you cannot do that (except as an early adoptor perhaps) for > > > Windows, OS X and probably quite a few others. In this regard VMS is > > > the > > > same. The only times I have acquired an early release of VMS were via > > > a > > > non-official looking tape from the local DEC/Compaq/HP office. > > > If you have the appropriate level MSDN contract with Microsoft, all of > > their products are available for download, both current and pre-release > > versions. > > > Microsoft charges more for actually shipping the CD-ROMS/DVDs. > > I stand corrected. > > -- > Paul Sture > > Sue's OpenVMS > bookmarks:http://eisner.encompasserve.org/~sture/ovms-bookmarks.html- Hide > quoted text - > > - Show quoted text - Following John M's comments further up this thread, I am right in thinking that it's ok backing up an installed system disk using BACKUP/ IMAGE/NOALIAS and this will give a working disk when restored, aren't I? Steve ------------------------------ Date: Sun, 13 Jan 2008 20:09:56 -0500 From: =?ISO-8859-1?Q?Arne_Vajh=F8j?= Subject: Re: OT - EISNER:: upgrade complete Message-ID: <478ab65e$0$90275$14726298@news.sunsite.dk> Crni Gorac wrote: > On Jan 13, 2:27 am, VAXman- @SendSpamHere.ORG wrote: >> I hope the original poster of this thread can figure out how to invoke VIM >> from the command procedure I posted. I'm not sure how to tell VIM to write >> out to the P2 filename. It's a no brainer to have it read the P1 filename. > > I haven't, and I decided to just stick with EDT for while. > Nevertheless, thanks for the script you posted - it helps to > understand the procedure. ... $ copy 'p1' 'tmpfnm' $ vim 'tmpfnm' $ copy 'tmpfnm' 'p2' ... or something like that should be able to solve it. I even think I many years ago saw a COM file to do that. Hmm. A google groups search reveals that *I* in 1994 posted the following: #The following procedure works for almost anything probably also for VI ! # #Create disk:[dir]mumble.COM as: # #$ IF P1 .NES. "" THEN COPY 'P1' 'P2' #$ DEFINE/NOLOG SYS$INPUT SYS$COMMAND #$ mumble 'P2' #$ EXIT # #In LOGIN.COM add: # #$ DEFINE/NOLOG MAIL$EDIT disk:[dir]mumble.COM # #The MAIL will use the mumble editor as mail-editor ! I would assume that I tested it back then ... Arne ------------------------------ Date: Sun, 13 Jan 2008 13:00:56 -0800 (PST) From: etmsreec@yahoo.co.uk Subject: Re: print queues and IP Message-ID: <66ff7ce4-e5aa-4a4d-aae4-8dbd9dbdb2b9@u10g2000prn.googlegroups.com> On 13 Jan, 12:01, Uusim=E4ki wrote: > H Vlems wrote: > > Yesterday I bought an Alpha Server 1200 5/400 (a blue one, not a white > > box alpha). Since it is too heavy to put it in the same room as the > > others as yet, it sits noisily in the living room. The only available > > printer there is an old HP2100 with an IP printserver. > > I want to create a printerqueue that allows me to print to that > > HP2100, its IP address is 10.0.0.102. > > IIRC the TCPIP$TELNETSYM processor is needed, but where do I put the > > IP address? > > Hans > > Why not use the DCPS? It is very easy to use and supports a wealth of > different printers and almost any type of connection. > It makes it possible to print PS etc. > > http://h71000.www7.hp.com/doc/82final/dcps/dcps025_release_notes.PDF > > And the Hobbyist license kit includes DCPS licenses. > > Kari Depends whether the HP 2100 has Postscript in it. Most of the HP printers that I've seen in the last ten years have Postscript as an added cost extra (often as a memory SIMM). The alternative way to look at the situation is that the printer would be able to decode whatever stream of data got fed to it if it was IP capable but wouldn't be able to print output from a DCPS queue if it didn't have Postscript in it. You pays your money and take syour choice. Steve ------------------------------ End of INFO-VAX 2008.027 ************************