Hello

I get "Trans99 - LRECL > 255 unsupported: file transfer canceled" when trying to receive a module file from the host.

Is there anything I can do or is this a known restriction??

In the end I used a tape - so no issue, just interested :-)

A

well, i think i should know. But it's been a long time ago that i wrote this code and i simply don't remember why there is this restriction. Sorry...

I get "Trans99 - LRECL > 255 unsupported: file transfer canceled" when
trying to receive a module file from the host.

Is there anything I can do or is this a known restriction?

Maybe you could get around the restriction by putting the module in a VMARC
archive file? These are 80 byte card images so there should be no problems
transferring them.

If you need to build the VMARC archive on the host, there is a C implemention
of VMARC called VMA which should be compilable on most platforms.

Regards,
Peter Coghlan.

Its on the six pack...
.. and I can't see why we need yet another pack program. ...
There are utilities in the files section to read and write CMS TAPE files,
and DISK DUMP files both of which are native VM archive formats, on
windows/linux

Dave

开云体育

Its on the six pack...
.. and I can't see why we need yet another pack program. ...
There are utilities in the files section to read and write CMS TAPE files,
and DISK DUMP files both of which are native VM archive formats, on
windows/linux

Not to start a debate, but I can see why.? :-)

• It's not trivial to mount a AWS tape on any system that you don't control the host
• When you do control the host, it requires accessing not just your VM systems but two Hercules consoles.
• VMARC data fits through card readers, and by extension host utilities that use TCP/IP to exploit the card reader, like vmsubmit.py in . (It's a pity Hercules card punches can't connect to pipes like printers can. I find this an odd omission.)
  
• Issues that apply in special cases (i.e. the LCM+L 4361, which of course I'm rather fond of):
  
• It's not trivial to mount a AWS tape on real hardware
• DISK (DUMP/LOAD) is not entirely compatible between VM/370 R6 and VM/SP 5
• IBM likes it.
  
• It seems it's their preferred format for sharing free VM software over the ASCII friendly Internet.?
  (Pity that most the software itself is for XA and newer!)
• It too has host utilities to read the format
  (Pity the MacOS version, being 32-bit, is broken on Catalina)
  

This is not to say the other toys should be tossed (except may the Windows specific one which requires shutting down VM and running a host script!), but it is useful.

-ahd-

p.s. I consider VMARC's command line syntax horrible, but I have to yet to decide what it should be (and if so, what wrapper script to write for it.)

-- 
Drew Derbyshire

 Alcohol, Tobacco, Firearms. Anyone remember the chips?

Its on the six pack...
.. and I can't see why we need yet another pack program. ...
There are utilities in the files section to read and write CMS TAPE files,
and DISK DUMP files both of which are native VM archive formats, on
windows/linux

It's just a suggestion :-)

I admit that the first time I came across a VMARC file, I moaned that here
was yet another file format that I needed to find tools to process.

However, I have very much come to like VMARC because it unlike CMS TAPE, it
does not have any filesystem type dependencies or CMS version dependencies
and unlike DISK DUMP, it can archive more than one file and unlike both, the
archive file is smaller than the original file(s). Also (and like DISK DUMP
archives), VMARC archives can trivially be sent through virtual and er, real
card readers and punches and across an NJE network.

I've even come up with a way to build VMARC on MUSIC to make it easier to
exchange files with that platform too (even though MUSIC has a utility to
read CMS TAPE files which seems to be more capable than CMS TAPE LOAD under
VM/370...)

Regards,
Peter Coghlan

开云体育

-- 

Drew Derbyshire

?

 Alcohol, Tobacco, Firearms. Anyone remember the chips?

开云体育

-- 

Drew Derbyshire

?

 Alcohol, Tobacco, Firearms. Anyone remember the chips?

On Thu, Jan 2, 2020 at 05:09 PM, hans.latz wrote:

well, i think i should know. But it's been a long time ago that i wrote this code and i simply don't remember why there is this restriction. Sorry...

Not to worry ... I can inspect the code myself :-)

Oh ... And sorry I am making my own home grown formatter ... I just wanted something super easy to move c source files back and forwards! ?

开云体育

I believe that Hercules does support socket readers.

?

?

via NETCAT as well as FISH’s HERCRDR and of course the SIXPACK has VMARC (not sure if its on the

?

I know Hercules supports socket readers.? I said Hercules didn't support punches into pipes, whereas Hercules does support printers into pipes.? A punch -> pipe -> socket reader setup would allow automated RSCS-like forwarding between systems. (Nobody said I wasn't a wee bit twisted.)

<plug>
vmsubmit.py exploits Hercules socket readers, has a fairly decent (read: idiot resistant) UX, and has internal features like EBCDIC support and detecting VMARC files so it doesn't translate them.? vmsubmit.py's primary limitation is being written in Python, which makes it less appealing to Windows users.?

(vmsubmit.py even can act as a SIFT client, which is not a protocol I recommend; that RFC escaped into the wild too young, and it was obviously designed in a more innocent age.? That's for the curious; it's supported on later versions of RSCS.)
</plug>

On Thu, Jan 2, 2020 at 08:01 PM, Drew Derbyshire wrote:

I said Hercules didn't support punches into pipes, whereas Hercules does support printers into pipes.

Is Hercules still supported by its amazing creators? I would have thought (without looking at the code!) that adding support to named pipes or TCP/IP sockets for the puncher or printer would be easy. In fact has anyone just tried to use named pipe, it might just work ...

On Thu, Jan 2, 2020 at 05:09 PM, hans.latz wrote:

well, i think i should know. But it's been a long time ago that i wrote this code and i simply don't remember why there is this restriction. Sorry...

Io-buffer has length 512 but 255 is hard coded as a check. I am thinking (considering cr lf and null) we should have it 512 - 3 as the max lrecl. In fact we should make it a define.

That's the file side ... What about the filetransfer? Unlimited or is there a max of 2k (I read something about 2048 somewhere in the docs?)

Thoughts?

Adrian

开云体育

开云体育

On Thu, Jan 2, 2020 at 08:01 PM, Drew Derbyshire wrote:

I said Hercules didn't support punches into pipes, whereas Hercules does support printers into pipes.

Is Hercules still supported by its amazing creators?

Hercules has owners. Check

I would have thought (without looking at the code!) that adding support to named pipes or TCP/IP sockets for the puncher or printer would be easy. In fact has anyone just tried to use named pipe, it might just work ...

Outside of the actual emulation code, it's all a simple matter of programming, but when you're working with a 211 K line codebase, one needs to take take care lest installing brighter lights in the chicken coop causes a blackout in the cow barn.?

-ahd-

On Fri, Jan 3, 2020 at 12:23 AM, Drew Derbyshire wrote:

but when you're working with a 211 K line codebase, one needs to take take care lest installing brighter lights in the chicken coop causes a blackout in the cow barn

Noted!