I had the (I thought) bright idea to attach a hercules device to a raspberry pi GPIO pin with"attach 30f 1403 /sys/class/gpio/gpio18/value"

I then ran a program to write either a 1 or 0 to that printer (directly, not through JES).This does actually work in that the LED goes on and off but I get the HHC01105E error message followed by an EQC MVS error and an abend which I imagine are secondary to whatever hercules is unhappy about. I've googled for the message and found one reference to invalid characters in printer output. The manual says the message is not documented. The only place I see HHC1105 in the source is in printer.c and it looks like an unsupported device type in the attach processing rather than at write time.

The console output follows then the C program that's doing the writing. How can I find out what's causing the error or get around it.

Post by ***@yahoo.com [hercules-390]This does actually work in that the LED goes on and off but I get theHHC01105E error message followed by an EQC MVS error and an abend whichI imagine are secondary to whatever hercules is unhappy about. I'vegoogled for the message and found one reference to invalid characters inprinter output. The manual says the message is not documented. The onlyplace I see HHC1105 in the source is in printer.c and it looks like anunsupported device type in the attach processing rather than at write time.

On real hardware a 1403 cannot be used until the UCS buffer is loaded.That's a function the operators used to perform with a stand-alone deck,and that's done by JES these days. Perhaps if you use the printer underJES, and then drain it, your direct write to the printer will work.

Ahh: that could be the kind of thing that's going on. I had picked on the 1403 thinking of it as a dumb printer. I'll try initializing it with jes or i'll try a different device type - i was originally planning on a card punch anyway.

haha - not solved but pretty simple: The GPIO process addressed by attach /sys/class/gpio/gpio18/value is happy to respond if you send a "1" or "0" but if you send anything else, you get the invalid argument response and subsequent equipment check.

I haven't figured how to solve it yet but i think it's doable and, on the upside, the CCW trace function is pretty splendid. I wish i'd had these tools(or this degree of access) when i was a working system programmer.