On 04/14/2015 11:00 AM, Paul_Koning at Dell.com wrote: 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. :-( I have no problem with hitting the books; I'm generally pretty self-sufficient in that regard, but I'm about to load these machines onto a truck and take them to VCF, so I'm just short of time. Things have gotten a bit less stressful about that since some hardware (not the 11/34) has started to behave, and now it looks like some of the machines will be on HECnet during the show, so I'll be able to get some software on them then. -Dave -- Dave McGuire, AK4HZ/3 New Kensington, PA

On 04/14/2015 11:28 AM, Cory Smelosky wrote: No, a presentation *involving* HECnet, to make it more interesting and functional. I would never do a presentation *about* HECnet without Johnny's involvement/participation, and likely that of the rest of the group as well. The hardware I am showing off is owned by me...HECnet is not. I am demoing a PDP-11/24, a PDP-11/34, a PDP-11/44, a PDP-8/e, and a VAX-8250. (it reboots...if you...print??) -Dave -- Dave McGuire, AK4HZ/3 New Kensington, PA

M Jordi Guillaumes Pons El 14/04/2015, a les 17:56, Cory Smelosky <b4 at gewt.net> va escriure:

El 14/04/2015, a les 17:25, Dave McGuire <mcguire at neurotica.com> va escriure: This is basically a wild guess... Have you tried to change the line terminators of your files at the Linux side? Try to convert them to 'DOS' style and see what happens. If the RSX FAL looks for a CR to split the records and it does not find it perhaps the result could be just what you are observing.

Don;t you figure, they were stream files on the source, and got laid byte for byte into files with variable length record type set on the RSX end, which would cause random pairs of bytes to be interpreted as record lengths? A look with dmp ti:=filename.ext /bl /as would let you see if they have record sizes that make sense. ----- Original Message ----- From: "Dave McGuire" <mcguire at neurotica.com> To: "hecnet" <hecnet at Update.UU.SE> Sent: Tuesday, April 14, 2015 10:25:36 AM Subject: Re: [HECnet] "illegal record size" in RSX? On 04/14/2015 11:00 AM, Paul_Koning at Dell.com wrote: 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. :-( I have no problem with hitting the books; I'm generally pretty self-sufficient in that regard, but I'm about to load these machines onto a truck and take them to VCF, so I'm just short of time. Things have gotten a bit less stressful about that since some hardware (not the 11/34) has started to behave, and now it looks like some of the machines will be on HECnet during the show, so I'll be able to get some software on them then. -Dave -- Dave McGuire, AK4HZ/3 New Kensington, PA

On 2015-04-15 06:58, Dave McGuire wrote: 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... 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. Of course, it might also be that the actual file contents are "funny", but I think not. Johnny

Stream-CR, interesting. I thought that you can adjust what Linux does, and a check of the manpage for dncopy confirms that. The default record format is stream -- which is fine for Linux and RSTS, not so much for RSX. To override it, add "-r var" to set the record format to variable, which is what RSX-like systems prefer. paul ________________________________________ From: owner-hecnet at Update.UU.SE [owner-hecnet at Update.UU.SE] on behalf of Dave McGuire [mcguire at neurotica.com] Sent: Wednesday, April 15, 2015 12:58 AM To: hecnet at Update.UU.SE Subject: Re: [HECnet] "illegal record size" in 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 -Dave -- Dave McGuire, AK4HZ New Kensington, PA

On 04/15/2015 11:13 AM, Johnny Billquist wrote: I've been down that road already. ;) Copying it to a VMS system works great and the file looks fine, but of course VMS is very good about Just Handling Things. Copying it in with dncopy -r var hangs for a long time, then exits saying "error closing output" on the Linux side. The resultant file on the RSX side is one line long, but the attributes are correct at least. (format = variable length) There's a trailing LF on that single line, even when using -d with dncopy. I have another VMS system that has an IP stack installed (AXPEE::), I will try to retrieve the file I'm using for testing via that, and copy it via DECnet from there to the RSX system. If that fails, I will try using MIM as Johnny offered. Thank you for the suggestions, guys. I appreciate everyone's help. Again I am usually pretty self-sufficient about these matters; I have the documentation and the skills to use it, but I am just short of time with much to do before departure. And it seems I've forgotten nearly everything about RSX. :-/ -Dave -- Dave McGuire, AK4HZ New Kensington, PA

On 2015-04-15 17:49, Dave McGuire wrote: Install TCP/IP on your RSX system, and FTP directly between them instead? (Assuming you have a recent 11M-PLUS system). Johnny

On 2015-04-15 18:02, Dave McGuire wrote: Ok. I assume you already have DECnet installed. Installing TCP/IP should actually be pretty simple and straight forward. Download the disk or tape - MIM::US:[FTP]. Extract the information (atleast if from tape), run IPGEN, and then you just need to invoke the startup scripts at boot, and probably config a few things in a couple of files to be up and running. It really should not be that hard. And of course, I can answer questions as well... :-) Johnny

On 04/15/2015 12:06 PM, Johnny Billquist wrote: Any idea of why I might get "access control rejected" when trying to get a directory of MIM::US:[FTP] from RSX, but not from VMS? I probably have something incorrectly configured in nft. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

On 04/15/2015 12:34 PM, Johnny Billquist wrote: Ok, that makes sense, thanks for the pointer. I will look that up and get it configured. While you're there, do you have a suggestion for the "path of least resistance" to install F77 and BP2 on this machine? I have the trailing-edge dists as .tpc files. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

On 2015-04-15 18:42, Johnny Billquist wrote: By the way, I hope you know that the BP2 V2.7 tape on trailing-edge is corrupt... The V2.5 tape is OK though. Johnny

IIRC it is necessary to hack a little bit the install command procedure of 2.5, since it invokes a small task builder which is not present in 4.6 M+.

On 2015-04-15 18:26, Dave McGuire wrote: Oh, yeah. Another simple way, if you don't want to futz with proxy acess... Try MIM"GUEST GUEST":: instead of just MIM:: Johnny

On 2015-04-15 17:41, Dave McGuire 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. Johnny