- HECnet - lists @ Update

by clemc＠ccc.com

I just scored a TSZ08 but it's differential SCSI. Amazingly, I found a DWZZB-AA SE to DE converter a few years ago, which I am hoping still works (I'll find out soon). The issue is that this is the first time I played with DE SCSI and have nothing else. Question 1. Anyway on know what the DEC cable number was for a 68 pin (male each end) SCSI cable? I think its BN31G-02 [i.e. this has the right connects on the end]. Any one know if that is correct. I think I have source for a couple of them. Also, I assume I need a differential SCSI terminator [everything I have now is SE]. Any idea what the DEC # was for the proper terminator. What I believe I need to need to connect it is: SCSI Single Ended (SE) HBA with 68 pin female: <--- 68 pin male -------------- 68 pin male -> DWZZB-AA SE side with 68 pin female TSZ08 Differential (DE) SIDE A with 68 pin female: <--- 68 pin male -------------- 68 pin male -> DWZZB-AA A DE side with 68 pin female TSZ08 Differential (DE) SIDE B with 68 pin female: Differential SCSI Terminator 68 pin male

10 years, 2 months

1
0
0 0

SC-40 Diagnostic Output

by b4＠gewt.net

Here it is! NSP>take acpt40.cmd NSP>SET CLOCK 300 [Clock speed=300] NSP>SET CPU DTE 0 FRONT-END NSP>SET CPU DTE 0 PRIVILEGED NSP>DEASSIGN CHANNEL 2 NSP>RUN/PASS:1000 DFKAA %Starting CPU0 ............................................ RUN/PASS:1000 DFKAB %Halting CPU0 %Starting CPU0 .......................... RUN/PASS:1000 DFKAC PDP-10 KL10 BASIC INSTRUCTION DIAGNOSTIC [DFKAB] %Halting CPU0 %Starting CPU0 ................................... RUN/PASS:1000 DFKAD PDP-10 KL10 BASIC INSTRUCTION DIAGNOSTIC [DFKAC] %Halting CPU0 %Starting CPU0 .................... RUN/PASS:1000 DFKBA PDP-10 KL10 BASIC INSTRUCTION DIAGNOSTIC [DFKAD] %Halting CPU0 %Starting CPU0 ............................................ RUN/PASS:1000 DFKBB PDP-10 KL10 BASIC INSTRUCTION RELIABILITY TEST 1 (DFKBA) %Halting CPU0 %Starting CPU0 .............. DECSYSTEM10 KL10 BASIC INSTRUCTION RELIABILITY TEST 2 (DFKBB) RUN/PASS:1000 DFKCA %Halting CPU0 %Starting CPU0 ..................................................... KL10 ADVANCED INSTRUCTION DIAGNOSTIC #1 RUN/PASS:1000 DFKCB %Halting CPU0 %Starting CPU0 ......................... RUN/PASS:1000 DFKCC DECSYSTEM KL10 ADVANCED INSTRUCTION DIAGNOSTIC #2 [DFKCB] %Halting CPU0 %Starting CPU0 ........................ RUN/PASS:1000 DFKDA DECSYSTEM10 KL10 ADVANCED INSTRUCTION DIAGNOSTIC #3 [DFKCC] %Halting CPU0 %Starting CPU0 ......................................... PDP-10 KL10 ARITHMETIC/RANDOM/INTERRUPT/MEMORY RELIABILITY TEST (DFKDA) RUN/PASS:1000 DFKEA %Halting CPU0 %Starting CPU0 ................... DECSYSTEM KL10 PAGING HARDWARE DIAGNOSTIC (DFKEA) RUN/PASS:1000 DFKEB %Halting CPU0 %Starting CPU0 ............... RUN/PASS:5 DFKEC DECSYSTEM KL10 MONITOR UUO AND MODE DIAGNOSTIC (DFKEB) %Halting CPU0 %Starting CPU0 ....................... RUN/PASS:1000 DFKED DECSYSTEM KL10 PXCT DIAGNOSTIC [DFKEC] %Halting CPU0 %Starting CPU0 ......................... SET CLOCK 275 DFKED - EXTENDED ADDRESSING TEST VERSION 0.0, SV=0.14, CPU#=2645, MCV=621, MCO=671, HO=36, 60HZ SWITCHES = 000000 000000 CLK SOURCE = NORMAL, CLK RATE = FULL, AC BLK 0 END PASS 1. [Clock speed=275]RUN/PASS:1000 DFKAA %Halting CPU0 %Starting CPU0 ............................................ RUN/PASS:1000 DFKAB %Halting CPU0 %Starting CPU0 .......................... RUN/PASS:1000 DFKAC PDP-10 KL10 BASIC INSTRUCTION DIAGNOSTIC [DFKAB] %Halting CPU0 %Starting CPU0 ................................... RUN/PASS:1000 DFKAD PDP-10 KL10 BASIC INSTRUCTION DIAGNOSTIC [DFKAC] %Halting CPU0 %Starting CPU0 .................... RUN/PASS:1000 DFKBA PDP-10 KL10 BASIC INSTRUCTION DIAGNOSTIC [DFKAD] %Halting CPU0 %Starting CPU0 ............................................ RUN/PASS:1000 DFKBB PDP-10 KL10 BASIC INSTRUCTION RELIABILITY TEST 1 (DFKBA) %Halting CPU0 %Starting CPU0 .............. RUN/PASS:1000 DFKCA DECSYSTEM10 KL10 BASIC INSTRUCTION RELIABILITY TEST 2 (DFKBB) %Halting CPU0 %Starting CPU0 ..................................................... RUN/PASS:1000 DFKCB KL10 ADVANCED INSTRUCTION DIAGNOSTIC #1 %Halting CPU0 %Starting CPU0 ......................... RUN/PASS:1000 DFKCC DECSYSTEM KL10 ADVANCED INSTRUCTION DIAGNOSTIC #2 [DFKCB] %Halting CPU0 %Starting CPU0 ........................ DECSYSTEM10 KL10 ADVANCED INSTRUCTION DIAGNOSTIC #3 [DFKCC] RUN/PASS:1000 DFKDA %Halting CPU0 %Starting CPU0 ......................................... RUN/PASS:1000 DFKEA PDP-10 KL10 ARITHMETIC/RANDOM/INTERRUPT/MEMORY RELIABILITY TEST (DFKDA) %Halting CPU0 %Starting CPU0 ................... RUN/PASS:1000 DFKEB DECSYSTEM KL10 PAGING HARDWARE DIAGNOSTIC (DFKEA) %Halting CPU0 %Starting CPU0 ............... RUN/PASS:5 DFKEC DECSYSTEM KL10 MONITOR UUO AND MODE DIAGNOSTIC (DFKEB) %Halting CPU0 %Starting CPU0 ....................... RUN/PASS:1000 DFKED DECSYSTEM KL10 PXCT DIAGNOSTIC [DFKEC] %Halting CPU0 %Starting CPU0 ......................... SET CLOCK 325 DFKED - EXTENDED ADDRESSING TEST VERSION 0.0, SV=0.14, CPU#=2645, MCV=621, MCO=671, HO=36, 60HZ SWITCHES = 000000 000000 CLK SOURCE = NORMAL, CLK RATE = FULL, AC BLK 0 END PASS 1. [Clock speed=325]RUN/PASS:1000 DFKAA %Halting CPU0 %Starting CPU0 ............................................ RUN/PASS:1000 DFKAB %Halting CPU0 %Starting CPU0 .......................... RUN/PASS:1000 DFKAC PDP-10 KL10 BASIC INSTRUCTION DIAGNOSTIC [DFKAB] %Halting CPU0 %Starting CPU0 ................................... RUN/PASS:1000 DFKAD PDP-10 KL10 BASIC INSTRUCTION DIAGNOSTIC [DFKAC] %Halting CPU0 %Starting CPU0 .................... PDP-10 KL10 BASIC INSTRUCTION DIAGNOSTIC [DFKAD] RUN/PASS:1000 DFKBA %Halting CPU0 %Starting CPU0 ............................................ RUN/PASS:1000 DFKBB PDP-10 KL10 BASIC INSTRUCTION RELIABILITY TEST 1 (DFKBA) %Halting CPU0 %Starting CPU0 .............. RUN/PASS:1000 DFKCA DECSYSTEM10 KL10 BASIC INSTRUCTION RELIABILITY TEST 2 (DFKBB) %Halting CPU0 %Starting CPU0 ..................................................... RUN/PASS:1000 DFKCB KL10 ADVANCED INSTRUCTION DIAGNOSTIC #1 %Halting CPU0 %Starting CPU0 ......................... RUN/PASS:1000 DFKCC DECSYSTEM KL10 ADVANCED INSTRUCTION DIAGNOSTIC #2 [DFKCB] %Halting CPU0 %Starting CPU0 ........................ RUN/PASS:1000 DFKDA DECSYSTEM10 KL10 ADVANCED INSTRUCTION DIAGNOSTIC #3 [DFKCC] %Halting CPU0 %Starting CPU0 ......................................... RUN/PASS:1000 DFKEA PDP-10 KL10 ARITHMETIC/RANDOM/INTERRUPT/MEMORY RELIABILITY TEST (DFKDA) %Halting CPU0 %Starting CPU0 ................... RUN/PASS:1000 DFKEB DECSYSTEM KL10 PAGING HARDWARE DIAGNOSTIC (DFKEA) %Halting CPU0 %Starting CPU0 ............... RUN/PASS:5 DFKEC DECSYSTEM KL10 MONITOR UUO AND MODE DIAGNOSTIC (DFKEB) %Halting CPU0 %Starting CPU0 ....................... RUN/PASS:1000 DFKED DECSYSTEM KL10 PXCT DIAGNOSTIC [DFKEC] %Halting CPU0 %Starting CPU0 ......................... SET CLOCK 300 DFKED - EXTENDED ADDRESSING TEST VERSION 0.0, SV=0.14, CPU#=2645, MCV=621, MCO=671, HO=36, 60HZ SWITCHES = 000000 000000 CLK SOURCE = NORMAL, CLK RATE = FULL, AC BLK 0 END PASS 1. [Clock speed=300]SET CPU DTE 1 FRONT-END ASSIGN CHANNEL 2 SET CPU DTE 0 RESTRICTED [Command file completed ACPT40.CMD] END PASS 101. END PASS 201. END PASS 301. END PASS 401. END PASS 501. END PASS 601. END PASS 701. END PASS 801. END PASS 901. [CPU0 1000 passes completed.] -- Cory Smelosky http://gewt.net Personal stuff http://gimme-sympathy.org Projects

10 years, 2 months

1
0
0 0

"illegal record size" in RSX?

by system＠TMESIS.COM

Johnny Billquist <bqt at softjar.se> writes: >On 2015-04-15 19:47, Brian Schenkenberger, VAXman- wrote: >> Johnny Billquist <bqt at softjar.se> writes: >> >>> On 2015-04-15 19:17, Brian Schenkenberger, VAXman- wrote: >>>> Dave McGuire <mcguire at neurotica.com> writes: >>>> >>>>> On 04/15/2015 11:58 AM, Johnny Billquist wrote: >>>>>> Seems to me you are just hitting the problems with the Linux DECnet >>>>>> code, since that has pretty much only been tested against VMS, and >>>>>> probably are breaking the protocol all over the place... >>>>>> I know that transferring stream files from VMS to RSX works fine, with >>>>>> RSX converting them to variable length records. >>>>>> Like I said before, I have had essentially no luck in using Linux DECnet >>>>>> against RSX systems. Not only file transfers, but things like PHONE also >>>>>> do not work. >>>>> >>>>> Yes, it looks like that's what's going on. That sucks. I would love >>>>> to pick up the maintenance of that code, but I don't know DECnet >>>>> internals at all and would be starting from scratch there. I know I >>>>> could handle the code, but the required time to come up to speed is an >>>>> obstacle. >>>> >>>> I have, printed, all DECnet (circa Pase IV) specs here; however, they are >>>> on-line if you Google them. >>> >>> Speaking of that, I became curious about a couple of details of the DAP >>> protocol when I was fixing the RSX implementation a while ago. >>> There are a couple of fields in that protocol that identifies the remote >>> operating system and remote file system, and obviously there are a whole >>> set of values these can have. I'd like to update those tables, but do >>> anyone have an fairly recent, authoritative source? >>> Also, RSX implements DAP V7.1, while VMS has DAP V7.2. Does anyone know >>> what the differences are? >> >> >> The DAP spec. V5.6.0 says: >> >> 0 - Illegal >> 1 - RT-11 >> 2 - RSTS/E >> 3 - RSX-11S >> 4 - RSX-11M >> 5 - RSX-11D >> 6 - IAS >> 7 - VAX/VMS >> 8 - TOPS-20 >> 9 - TOPS-10 >> 10- RTS-8 >> 11- OS-8 >> 12- RSX-11M+ >> 13- COPOS/11 (TOPS-20 Front End) >> >> I checked in LIB.REQ on VMS V8.4 and there are only symbolic definitions for >> the first 5: >> >> literal NMA$C_SYS_RST = 1; ! Rsts >> literal NMA$C_SYS_RSX = 2; ! Rsx family >> literal NMA$C_SYS_TOP = 3; ! Tops-20 >> literal NMA$C_SYS_VMS = 4; ! Vms >> literal NMA$C_SYS_RT = 5; ! RT-11 > >That was even less than what RSX knows... >In NFT or RSX, I can see the following: >1 - RT-11 >2 - RSTS/E >3 - RSX-11S >4 - RSX-11M >5 - RSX-11D >6 - IAS >7 - VAX/VMS >8 - TOPS-20 >9 - TOPS-10 >10 - RTS-8 >11 - OS-8 >12 - RSX-11M+ >13 - COPOS/11 (TOPS-20 frontend) >14 - P/OS >15 - VAXELAN >16 - CP/M >17 - MS-DOS >18 - Ultrix-32 >19 - Ultrix-11 >20 - DTF/MVS > >And I discovered that Windows NT seems to have the number 25, but I have >no idea about 21-24. > >And for filesystems, RSX knows: >1 - RMS-11 >2 - RMS-20 >3 - RMS-32 >4 - FCS-11 >5 - RT-11 >6 - No file system >7 - TOPS-20 >8 - TOPS-10 >9 - OS-8 >10 - RMS-32S >11 - CP/M >12 - MS-DOS >13 - Ultrix-32 >14 - Ultrix-11 >15 - DTF/MVS I've had my head deep in the RMS internals and I should have recalled this. The XAB (eXtrended Attributes Block) defines: literal XAB$K_RT11 = 1; literal XAB$K_RSTS = 2; literal XAB$K_RSX11S = 3; literal XAB$K_RSX11M = 4; literal XAB$K_RSX11D = 5; literal XAB$K_IAS = 6; literal XAB$K_VAXVMS = 7; literal XAB$K_TOPS20 = 8; literal XAB$K_TOPS10 = 9; literal XAB$K_RTS8 = 10; literal XAB$K_OS8 = 11; literal XAB$K_RSX11MP = 12; literal XAB$K_COPOS11 = 13; literal XAB$K_P_OS = 14; literal XAB$K_VAXELN = 15; literal XAB$K_CPM = 16; literal XAB$K_MS_DOS = 17; literal XAB$K_ULTRIX_32 = 18; literal XAB$K_ULTRIX_11 = 19; literal XAB$K_RMS11 = 1; literal XAB$K_RMS20 = 2; literal XAB$K_RMS32 = 3; literal XAB$K_FCS11 = 4; literal XAB$K_RT11FS = 5; literal XAB$K_NO_FS = 6; literal XAB$K_TOPS20FS = 7; literal XAB$K_TOPS10FS = 8; literal XAB$K_OS8FS = 9; literal XAB$K_RMS32S = 10; literal XAB$K_CPMFS = 11; literal XAB$K_MS_DOSFS = 12; literal XAB$K_ULTRIX32_FS = 13; literal XAB$K_ULTRIX11_FS = 14; -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG I speak to machines with the voice of humanity.

10 years, 2 months

3
3
0 0

"illegal record size" in RSX?

by system＠TMESIS.COM

Dave McGuire <mcguire at neurotica.com> writes: >On 04/15/2015 11:58 AM, Johnny Billquist wrote: >> Seems to me you are just hitting the problems with the Linux DECnet >> code, since that has pretty much only been tested against VMS, and >> probably are breaking the protocol all over the place... >> I know that transferring stream files from VMS to RSX works fine, with >> RSX converting them to variable length records. >> Like I said before, I have had essentially no luck in using Linux DECnet >> against RSX systems. Not only file transfers, but things like PHONE also >> do not work. > > Yes, it looks like that's what's going on. That sucks. I would love >to pick up the maintenance of that code, but I don't know DECnet >internals at all and would be starting from scratch there. I know I >could handle the code, but the required time to come up to speed is an >obstacle. I have, printed, all DECnet (circa Pase IV) specs here; however, they are on-line if you Google them. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG I speak to machines with the voice of humanity.

10 years, 2 months

3
3
0 0

"illegal record size" in RSX?

by system＠TMESIS.COM

Johnny Billquist <bqt at softjar.se> writes: >On 2015-04-15 19:17, Brian Schenkenberger, VAXman- wrote: >> Dave McGuire <mcguire at neurotica.com> writes: >> >>> On 04/15/2015 11:58 AM, Johnny Billquist wrote: >>>> Seems to me you are just hitting the problems with the Linux DECnet >>>> code, since that has pretty much only been tested against VMS, and >>>> probably are breaking the protocol all over the place... >>>> I know that transferring stream files from VMS to RSX works fine, with >>>> RSX converting them to variable length records. >>>> Like I said before, I have had essentially no luck in using Linux DECnet >>>> against RSX systems. Not only file transfers, but things like PHONE also >>>> do not work. >>> >>> Yes, it looks like that's what's going on. That sucks. I would love >>> to pick up the maintenance of that code, but I don't know DECnet >>> internals at all and would be starting from scratch there. I know I >>> could handle the code, but the required time to come up to speed is an >>> obstacle. >> >> I have, printed, all DECnet (circa Pase IV) specs here; however, they are >> on-line if you Google them. > >Speaking of that, I became curious about a couple of details of the DAP >protocol when I was fixing the RSX implementation a while ago. >There are a couple of fields in that protocol that identifies the remote >operating system and remote file system, and obviously there are a whole >set of values these can have. I'd like to update those tables, but do >anyone have an fairly recent, authoritative source? >Also, RSX implements DAP V7.1, while VMS has DAP V7.2. Does anyone know >what the differences are? The DAP spec. V5.6.0 says: 0 - Illegal 1 - RT-11 2 - RSTS/E 3 - RSX-11S 4 - RSX-11M 5 - RSX-11D 6 - IAS 7 - VAX/VMS 8 - TOPS-20 9 - TOPS-10 10- RTS-8 11- OS-8 12- RSX-11M+ 13- COPOS/11 (TOPS-20 Front End) I checked in LIB.REQ on VMS V8.4 and there are only symbolic definitions for the first 5: literal NMA$C_SYS_RST = 1; ! Rsts literal NMA$C_SYS_RSX = 2; ! Rsx family literal NMA$C_SYS_TOP = 3; ! Tops-20 literal NMA$C_SYS_VMS = 4; ! Vms literal NMA$C_SYS_RT = 5; ! RT-11 -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG I speak to machines with the voice of humanity.

10 years, 2 months

2
1
0 0

"illegal record size" in RSX?

by mcguire＠neurotica.com

Hey folks. I'm moving some text files to an RSX system via DECnet under Linux. The files on the RSX system are not readable; I get "illegal record size" when trying to type them. Has anyone hit this? I assume there's a simple solution.. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

10 years, 2 months

7
37
0 0

"illegal record size" in RSX?

by system＠TMESIS.COM

Johnny Billquist <bqt at softjar.se> writes: >On 2015-04-15 12:43, Brian Schenkenberger, VAXman- wrote: >> Johnny Billquist <bqt at softjar.se> writes: >> >>> On 2015-04-15 06:58, Dave McGuire wrote: >>>> On 04/14/2015 12:24 PM, Johnny Billquist wrote: >>>>> On 2015-04-14 04:53, Dave McGuire wrote: >>>>>> >>>>>> Hey folks. I'm moving some text files to an RSX system via DECnet >>>>>> under Linux. The files on the RSX system are not readable; I get >>>>>> "illegal record size" when trying to type them. >>>>>> >>>>>> Has anyone hit this? I assume there's a simple solution.. >>>>> >>>>> I have never had any luck at all transferring files from Linux to RSX. >>>>> >>>>> That said, what do you see if you do a DSP <file> under RSX? >>>> >>>> Just got back from road trip #1, only have a moment, will get back to >>>> this in the morning. Here is the DSP output: >>>> >>>> $ dsp forth.mac >>>> >>>> DU:[10,1]FORTH.MAC;1 >>>> Size: 139./144. Created: 15-APR-2015 00:54 >>>> Owner: [001,010] Revised: 15-APR-2015 00:55 >>>> File ID: (5601,10,0) Expires: <none_specified> >>>> File protection: System:RWED, Owner:RWED, Group:RWED, World:R >>>> File organization: Sequential >>>> File attributes: Allocation=144, Extend=0 >>>> Record format: Stream, maximum 255 bytes >>>> Record attributes: Carriage return >>> >>> Cool. So the first, and most obvious, problem, is that the file is >>> indeed in stream format. So no ordinary RSX tool will touch it with a >>> five foot pole... >> >> Really? So, we surely HAVE come a long way baby with VMS RMS! Still, any >> stream format is a ridiculously lame way to differentiate records IMHO. > >Yes. Good and bad - RMS is very much embedded within VMS. >In RSX, RMS is a library that you link in to any programs that wants it. >And it's not the only kid in town. You also have FCS, which is a >simpler, smaller library. The file formats are compatible between FCS >and RMS, as far as FCS capabilities cover them. FCS do not handle >indexed files, nor stream files. > >And all RSX tools use FCS. (Long story, but FCS was around before RMS >even existed, and RMS is an optional component, so it might not even >exist on all RSX systems.) > >>> Had you been pulling it from Linux to RSX, and initiated to transfer >>>from the RSX side, you can tell NFT exactly what format you want for the >>> file on the local side, when the remote side is a stream format file. >>> Not sure Linux can do that if you do the transfer from the Linux side. >>> >>> My next suggestion is to read up on RMSCNV, on how to convert the file. >>> I can never remember exactly how to use it, so I have to read every time >>> I want to, but it can convert the file to another format for you. >> >> I can't comment there either; however, if VMS CONVERT help is needed, I'm >> available. > >I believe that VMS CONVERT is pretty much the same deal as RMSCNV, but I >bet the exact syntax differs. :-) > >> And now, back to RMS CDC. > >I know "RMS", and I know "CDC", I just can't place them in the same >sentence. I must be missing something... I'd bet that if you Googled RMSCDC, you'd get your answer. It's an effort I've been working on since mid-2009 to allow Attunity to get access to changed data in RMS files by VMS applications using RMS (indexed file data was the primary goal but no file format or record format has been excluded). Some fun (not really, a real head-scratcher it's been) recently when my RMS CDC code was stressed tested with a 32 processor Itanium blade. FYI, what I provide is the VMS magic seen in this "graphic" in the gray box on the left. http://www.attunity.com/sites/default/files/content/Attunity%20Stream%20for… There's nothing specific to Attunity's process/products. RMSCDC is simply a log (a sequential record log of all RMS data changes. It's coordinated in a cluster environment too, so that in the shared file environment of the OepnVMS cluster, nothing is logged out of sync. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG I speak to machines with the voice of humanity.

10 years, 2 months

1
0
0 0

"illegal record size" in RSX?

by system＠TMESIS.COM

Johnny Billquist <bqt at softjar.se> writes: >On 2015-04-15 06:58, Dave McGuire wrote: >> On 04/14/2015 12:24 PM, Johnny Billquist wrote: >>> On 2015-04-14 04:53, Dave McGuire wrote: >>>> >>>> Hey folks. I'm moving some text files to an RSX system via DECnet >>>> under Linux. The files on the RSX system are not readable; I get >>>> "illegal record size" when trying to type them. >>>> >>>> Has anyone hit this? I assume there's a simple solution.. >>> >>> I have never had any luck at all transferring files from Linux to RSX. >>> >>> That said, what do you see if you do a DSP <file> under RSX? >> >> Just got back from road trip #1, only have a moment, will get back to >> this in the morning. Here is the DSP output: >> >> $ dsp forth.mac >> >> DU:[10,1]FORTH.MAC;1 >> Size: 139./144. Created: 15-APR-2015 00:54 >> Owner: [001,010] Revised: 15-APR-2015 00:55 >> File ID: (5601,10,0) Expires: <none_specified> >> File protection: System:RWED, Owner:RWED, Group:RWED, World:R >> File organization: Sequential >> File attributes: Allocation=144, Extend=0 >> Record format: Stream, maximum 255 bytes >> Record attributes: Carriage return > >Cool. So the first, and most obvious, problem, is that the file is >indeed in stream format. So no ordinary RSX tool will touch it with a >five foot pole... Really? So, we surely HAVE come a long way baby with VMS RMS! Still, any stream format is a ridiculously lame way to differentiate records IMHO. >Had you been pulling it from Linux to RSX, and initiated to transfer >from the RSX side, you can tell NFT exactly what format you want for the >file on the local side, when the remote side is a stream format file. >Not sure Linux can do that if you do the transfer from the Linux side. > >My next suggestion is to read up on RMSCNV, on how to convert the file. >I can never remember exactly how to use it, so I have to read every time >I want to, but it can convert the file to another format for you. I can't comment there either; however, if VMS CONVERT help is needed, I'm available. And now, back to RMS CDC. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG I speak to machines with the voice of humanity.

10 years, 2 months

2
1
0 0

PDP-11 Pascal or Modula-2?

by bob＠jfcl.com

Does anyone have the sources (I need the sources, not just binaries) for either the PDP-11 Pascal or Modula-2 compilers? It's probably on some DECUS tape somewhere, but I'm hoping someone can save me the trouble of searching. BTW, I have the sources (and working binaries) for the VAX/VMS Modula-2 compiler if anybody wants it. The VAX version was adapted from the PDP-11 version, and I'd like to find the original if I can. Thanks, Bob

10 years, 2 months

5
9
0 0

SC-40 update: Directory listing!

by b4＠gewt.net

Hey, Finally got a directory listing of the FE disk... .dir 40fe:[*,*,*,*,*] 1,1 1 <555> 8-Sep-95 40FE: [1,1] 1,4 1 <755> 8-Sep-95 3,3 0 <700> 8-Sep-95 1,2 1 <754> 8-Sep-95 3,6 0 <766> 8-Sep-95 3,11 0 <700> 8-Sep-95 3,7 0 <700> 8-Sep-95 1,340 1 <754> 31-Mar-97 Total of 4 blocks in 8 files on 40FE: [1,1] SAT SYS 109 <555> 8-Sep-95 [1,4] HOME SYS 19 <555> 8-Sep-95 BADBLK SYS 4 <557> 8-Sep-95 MARSFE SYS 5002 <057> 30-Jul-97 Total of 5134 blocks in 4 files on 40FE: [1,4] %DRTIDE Error reading 40FE:[1,2]RESTOR.EXE; I/O status = 400014 (Improper mode) RESTOR EXE 84 <057> 2-Nov-94 3A(52) [1,2] %DRTIDE Error reading 40FE:[1,2]FILSAV.EXE; I/O status = 400014 (Improper mode) FILSAV EXE 128 <666> 12-Sep-88 %DRTIDE Error reading 40FE:[1,2]MSFILE.EXE; I/O status = 400014 (Improper mode) MSFILE EXE 64 <057> 7-Mar-94 12(24) Total of 276 blocks in 3 files on 40FE: [1,2] A OUT 506 <057> 29-Jan-96 [1,340] NCP MCS 217 <057> 13-Jan-95 SX BIN 73 <057> 30-Aug-94 SX MCS 27 <057> 12-Dec-93 FX OLD 51 <057> 21-Oct-94 N1LX 609 501 <057> 2-Mar-94 N1LX REL 20 <057> 1-Mar-94 N1LX ULD 502 <057> 30-Sep-94 %DRTIDE Error reading 40FE:[1,340]BOOT40.EXE; I/O status = 400014 (Improper mode ) BOOT40 EXE 24 <057> 10-Nov-94 25B(161) %DRTIDE Error reading 40FE:[1,340]DEBKVB.EXE; I/O status = 400014 (Improper mode ) DEBKVB EXE 96 <057> 10-Nov-94 CPYFE COM 3 <057> 1-Apr-96 PINI40 CMD 1 <057> 2-Mar-94 %DRTIDE Error reading 40FE:[1,340]DFKAA.EXE; I/O status = 400014 (Improper mode) DFKAA EXE 176 <057> 27-Mar-85 %DRTIDE Error reading 40FE:[1,340]DFKAB.EXE; I/O status = 400014 (Improper mode) DFKAB EXE 104 <057> 29-Jan-85 %DRTIDE Error reading 40FE:[1,340]DFKAC.EXE; I/O status = 400014 (Improper mode) DFKAC EXE 140 <057> 17-Aug-88 %DRTIDE Error reading 40FE:[1,340]DFKAD.EXE; I/O status = 400014 (Improper mode) DFKAD EXE 80 <057> 29-Jan-85 %DRTIDE Error reading 40FE:[1,340]DFKBA.EXE; I/O status = 400014 (Improper mode) DFKBA EXE 176 <057> 3-Apr-85 %DRTIDE Error reading 40FE:[1,340]DFKBB.EXE; I/O status = 400014 (Improper mode) DFKBB EXE 56 <057> 3-Apr-85 %DRTIDE Error reading 40FE:[1,340]DFKCA.EXE; I/O status = 400014 (Improper mode) DFKCA EXE 212 <057> 29-Jan-85 %DRTIDE Error reading 40FE:[1,340]DFKCB.EXE; I/O status = 400014 (Improper mode) DFKCB EXE 100 <057> 29-Jan-85 %DRTIDE Error reading 40FE:[1,340]DFKCC.EXE; I/O status = 400014 (Improper mode) DFKCC EXE 96 <057> 4-Jun-85 %DRTIDE Error reading 40FE:[1,340]DFKDA.EXE; I/O status = 400014 (Improper mode) DFKDA EXE 164 <057> 3-Apr-85 %DRTIDE Error reading 40FE:[1,340]DFKEA.EXE; I/O status = 400014 (Improper mode) DFKEA EXE 76 <057> 18-Apr-85 %DRTIDE Error reading 40FE:[1,340]DFKEB.EXE; I/O status = 400014 (Improper mode) DFKEB EXE 60 <057> 3-Apr-85 %DRTIDE Error reading 40FE:[1,340]DFKEC.EXE; I/O status = 400014 (Improper mode) DFKEC EXE 92 <057> 2-May-85 %DRTIDE Error reading 40FE:[1,340]DFKED.EXE; I/O status = 400014 (Improper mode) DFKED EXE 100 <057> 3-May-85 %DRTIDE Error reading 40FE:[1,340]DFKFB.EXE; I/O status = 400014 (Improper mode) DFKFB EXE 56 <057> 29-Jan-85 ACPT40 CMD 2 <057> 30-Mar-94 PM CMD 1 <057> 24-Mar-93 PMDTE CMD 1 <057> 18-Jun-92 SYSDTE CMD 1 <057> 24-Mar-93 %DRTIDE Error reading 40FE:[1,340]SYSEX.EXE; I/O status = 400014 (Improper mode) SYSEX EXE 136 <057> 30-Oct-94 FX BIN 51 <055> 21-Feb-97 Total of 3901 blocks in 33 files on 40FE: [1,340] Grand total of 9315 blocks in 48 files Still not quite right and I can't access any files... .type 40fe:[1,340]pm.cmd ?Input device 40FE: file PM.CMD Status bits 400001 (Device write-locked or 7-9 punch not found on binary card) .copy pm.cmd=40fe:[1,340]pm.cmd ?Input device 40FE: file PM.CMD Status bits 400001 (Device write-locked or 7-9 punch not found on binary card) -- Cory Smelosky http://gewt.net Personal stuff http://gimme-sympathy.org Projects

10 years, 2 months

1
0
0 0

"illegal record size" in RSX?

by mcguire＠neurotica.com

An HTML attachment was scrubbed... URL: <http://lists.sonic.net/pipermail/hecnet-list/attachments/20150413/62f38cee/…>

10 years, 2 months

4
3
0 0

"illegal record size" in RSX?

by system＠TMESIS.COM

Dave McGuire <mcguire at neurotica.com> writes: >On 04/14/2015 11:53 AM, Jordi Guillaumes i Pons wrote: >>=20 >> El 14/04/2015, a les 17:25, Dave McGuire <mcguire at neurotica.com> va esc= >riure: >>> On 04/14/2015 11:00 AM, Paul_Koning at Dell.com wrote: >>>>> Hey folks. I'm moving some text files to an RSX system via DECnet=20 >>>>> under Linux. The files on the RSX system are not readable; I get=20 >>>>> "illegal record size" when trying to type them. >>>>> >>>>> Has anyone hit this? I assume there's a simple solution.. >>>> >>>> What are the RMS attributes? (I don=E2=80=99t know how to ask RSX to= > show >>>> those, unfortunately.) A possible way to get this would be a file >>>> with =E2=80=9Cno-span=E2=80=9D records and recordsize > 512. >>> >>> I don't know how to ask RSX for that...I used to be a heavy user of >>> RSX, but that was in the 80s; I seem to have forgotten nearly >>> everything. :-( >>> >>=20 >> This is basically a wild guess... Have you tried to change the line ter= >minators of your files at the Linux side? Try to convert them to 'DOS' st= >yle and see what happens. If the RSX FAL looks for a CR to split the reco= >rds and it does not find it perhaps the result could be just what you are= > observing. > > Yup, tried that...no change. :-( I'm working RMS right now but it is, of course, VMS. Can you get the file copied to a VMS system? -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG I speak to machines with the voice of humanity.

10 years, 2 months

1
0
0 0

"illegal record size" in RSX?

by mcguire＠neurotica.com

An HTML attachment was scrubbed... URL: <http://lists.sonic.net/pipermail/hecnet-list/attachments/20150413/c28b6a5a/…>

10 years, 2 months

2
1
0 0

RE: [DECtec] DEC Legacy 2015 Pictures

by robert.jarratt＠ntlworld.com

> -----Original Message----- > From: DECtec [mailto:dectec-bounces at dectec.info] On Behalf Of Mark > Wickens > Sent: 13 April 2015 22:15 > To: DEC discussion list.; hecnet at update.uu.se; cctalk at classiccmp.org > Subject: [DECtec] DEC Legacy 2015 Pictures > > I've uploaded some photos from the 2015 DEC Legacy event: > http://wickensonline.co.uk/declegacy/image > > Had a great time - already looking forward to the next one. Many thanks to the > presenters (local and remote) and everyone who attended. > > Regards, Mark. > > p.s. yes, I will try and get a better gallery tool embedded into the DEC Legacy > site. The drupal one I'm currently using sucks. > > > -- Thank you Mark for continuing to organise this event. I always look forward to it and can't wait for the next one. Regards Rob

10 years, 2 months

1
0
0 0

IA64 layered products?

by b4＠gewt.net

Hey, Are there any copies of the IA64 layered products out on HECnet? I can't seem to find an LP image containing C. -- Cory Smelosky http://gewt.net Personal stuff http://gimme-sympathy.org Projects

10 years, 3 months

3
6
0 0

gnuplot binaries

by mcguire＠neurotica.com

Does anyone here have gnuplot binaries for VMS on VAX? I could compile it, but I would like to be saved that time if possible. -Dave -- Dave McGuire, AK4HZ/3 New Kensington, PA

10 years, 3 months

4
10
0 0

Stupid question - relative time to make SUBMIT/AFTER= work after 3 hours

by sampsa＠mac.com

I have a script I want to have resubmit itself to run every 3 hours, but can't get the relative time right... What is the correct syntax for /AFTER= to say "3 hours from now"..? sampsa

10 years, 3 months

5
13
0 0

No subject

by bogus＠does.not.exist.com

.ncp sho act are Active areas summary as of 27-SEP-14 12:24:04 Next Area State Circuit Node 1 Reachable 1.13 (MIM) 5 Reachable UNA-0 5.1023 (A5RTR) 8 Reachable UNA-0 8.400 (GORVAX) 9 Reachable UNA-0 42.1022 (HUB) 11 Reachable UNA-0 11.2 (MAISA) 12 Reachable UNA-0 42.1022 (HUB) 14 Reachable UNA-0 14.4 (SKHNGW) 23 Reachable UNA-0 59.11 (DIMMA) 28 Reachable UNA-0 28.41 (RULLFS) 42 Reachable UNA-0 42.1022 (HUB) 44 Reachable UNA-0 44.1023 (A44RTR) 47 Reachable UNA-0 47.556 (KUHAVX) 59 Reachable UNA-0 59.11 (DIMMA) 61 Reachable UNA-0 42.1022 (HUB) 62 Reachable UNA-0 62.637 (CTAKAH) Johnny On 2014-09-26 16:44, Jordi Guillaumes i Pons wrote: Hello, My vision of HECNET is partial: [BITXOV]$ sh net/old OpenVMS Network status for local node 7.60 BITXOV on 26-SEP-2014 16:24:06.82 Area Cost Hops Next Hop to Area 3 3 2 TCP-1-9 -> 19.41 SG1 7 0 0 (Local) -> 7.60 BITXOV 19 2 1 TCP-1-9 -> 19.41 SG1 20 3 2 TCP-1-9 -> 19.41 SG1 Node Links Cost Hops Next Hop to Node 7.6 MBSERV 0 4 1 QNA-0 -> 7.6 MBSERV 7.61 BITXOO 0 4 1 QNA-0 -> 7.61 BITXOO 7.70 BITXOT 0 4 1 QNA-0 -> 7.70 BITXOT 7.71 BITXOR 0 4 1 QNA-0 -> 7.71 BITXOR 7.72 BITXOM 0 4 1 QNA-0 -> 7.72 BITXOM 7.74 BITXOW 0 4 1 QNA-0 -> 7.74 BITXOW 7.75 BITXA1 0 4 1 QNA-0 -> 7.74 BITXOW 7.76 BITXOX 0 4 1 QNA-0 -> 7.76 BITXOX 7.77 BITXOY 0 4 1 QNA-0 -> 7.77 BITXOY 7.79 BITXT0 0 4 1 QNA-0 -> 7.79 BITXT0 7.80 BITXT1 0 9 2 QNA-0 -> 7.61 BITXOO 7.81 BITXOZ 0 4 1 QNA-0 -> 7.81 BITXOZ Total of 12 nodes. It looks like SG1 does not have full connectivity. Jordi Guillaumes i Pons jg at jordi.guillaumes.name HECnet: BITXOV::JGUILLAUMES -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

10 years, 3 months

1
0
0 0

No subject

by bogus＠does.not.exist.com

Circuit QNA-0, Dropped by adjacent node, Adjacent node = 5.1023 (A5RTR) %<----------%<---------%<---------- followed some time later by... %<----------%<---------%<---------- %%%%%%%%%%% OPCOM 22-SEP-2014 08:46:14.06 %%%%%%%%%%% Message from user DECNET on SIMVAX DECnet event 4.15, adjacency up

10 years, 3 months

1
0
0 0

No subject

by bogus＠does.not.exist.com

Circuit QNA-0, Adjacent node = 5.1023 (A5RTR) %<----------%<---------%<---------- During the up/down cycle I do see messages being generated by the brige: %<----------%<---------%<---------- Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 %<----------%<---------%<---------- The bridge is connected to the outside world via a NAT rule in my Mikrotik router. Sorry for the long post! I've tried to be as comprehensive as I can be! Thanks for the help, Mark.

10 years, 3 months

1
0
0 0

No subject

by bogus＠does.not.exist.com

Circuit QNA-0, Dropped by adjacent node, Adjacent node = 5.1023 (A5RTR) %<----------%<---------%<---------- followed some time later by... %<----------%<---------%<---------- %%%%%%%%%%% OPCOM 22-SEP-2014 08:46:14.06 %%%%%%%%%%% Message from user DECNET on SIMVAX DECnet event 4.15, adjacency up

10 years, 3 months

1
0
0 0

No subject

by bogus＠does.not.exist.com

Circuit QNA-0, Adjacent node = 5.1023 (A5RTR) %<----------%<---------%<---------- During the up/down cycle I do see messages being generated by the brige: %<----------%<---------%<---------- Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 %<----------%<---------%<---------- The bridge is connected to the outside world via a NAT rule in my Mikrotik router. Sorry for the long post! I've tried to be as comprehensive as I can be! Thanks for the help, Mark.

10 years, 3 months

1
0
0 0

No subject

by bogus＠does.not.exist.com

Circuit QNA-0, Dropped by adjacent node, Adjacent node = 5.1023 (A5RTR) %<----------%<---------%<---------- followed some time later by... %<----------%<---------%<---------- %%%%%%%%%%% OPCOM 22-SEP-2014 08:46:14.06 %%%%%%%%%%% Message from user DECNET on SIMVAX DECnet event 4.15, adjacency up

10 years, 3 months

1
0
0 0

No subject

by bogus＠does.not.exist.com

Circuit QNA-0, Adjacent node = 5.1023 (A5RTR) %<----------%<---------%<---------- During the up/down cycle I do see messages being generated by the brige: %<----------%<---------%<---------- Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 Setting existing hash to bridge 1 %<----------%<---------%<---------- The bridge is connected to the outside world via a NAT rule in my Mikrotik router. Sorry for the long post! I've tried to be as comprehensive as I can be! Thanks for the help, Mark.

10 years, 3 months

1
0
0 0

No subject

by bogus＠does.not.exist.com

Circuit QNA-0, Dropped by adjacent node, Adjacent node = 5.1023 (A5RTR) %<----------%<---------%<---------- followed some time later by... %<----------%<---------%<---------- %%%%%%%%%%% OPCOM 22-SEP-2014 08:46:14.06 %%%%%%%%%%% Message from user DECNET on SIMVAX DECnet event 4.15, adjacency up

10 years, 3 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet