![]() | |
#31
| |||
| |||
|
|
"Mark Brown" wrote DUMMY = OCONV(STR,"U3F") will send STR to the printer. DUMMY is just so the oconv construct will work. U3F is an OA user exit, but it was Pick Systms big push to handle soft fonts for HP printers. I can't imagine them not implementing it in mvE. Mark Brown rsine (AT) stationeryhouse (DOT) com> wrote It doesn't seem that mvEnterprise supports the U3f user exit (or I am using it incorrectly). I duplicated your example but nothing goes to the printer. Dunno... maybe MVE wants a PRINTER ON to be in effect? try it with "U3F" and with "u3f" heck, also try "U003F" and "u003f" -- I notice the few example user-exits in the chapter 10 User Reference Manual are all Unnnn format. does MVE barf if you try for j=11 to 99 dummy=oconv('41','U':j) next j -- I mean, odds are those are NOT all legit user exit codes. It may silently ignore the bad codes, but if not, that'll tell you whether or not U3F is provided in your MVE release. I presume your MVE is a large application running on top of an operating system, perhaps AIX. Perhaps you could delegate this binary nastiness to some filter program outside of MVE {In D3 on linux or sco or aix, we give a native lp or lpr command when starting a shared printer, but can get more devious when inline data filtering is needed, say using sed or awk or tr. Or we can send the print stream to a whole other server on the LAN, and let IT filter the data with tools local to itself.} As far as I know, char(255) is the only bit pattern that really causes trouble. |
#32
| |||
| |||
|
|
Frank, Tried all of your suggestions and having no joy. When I tried "u003f", mvEnterprise recognized this as an illegal conversion code but reports nothing for "U3f". So, I am guessing the latter is a legal user exit but mvEnterprise simply ignores it. Thoughts? Thanks for giving feedback -- you're helping some poor sole google this out |
#33
| |||
| |||
|
|
rsine (AT) stationeryhouse (DOT) com> wrote Frank, Tried all of your suggestions and having no joy. When I tried "u003f", mvEnterprise recognized this as an illegal conversion code but reports nothing for "U3f". So, I am guessing the latter is a legal user exit but mvEnterprise simply ignores it. Thoughts? Thanks for giving feedback -- you're helping some poor sole google this out in future. The only other idea I had was see if the user exit 3f is used in the dm account bp file -- on d3/linux I notice the DOWNLOAD command has it. So log in to dm and do SORT BP WITH ANY = "[3f]" ANY and look for u3f or u003f matches. Or if you've got a BP DOWNLOAD source code item, see how _they_ send binary stuff to the printer; even if they don't rely on u3f then they must be doing it some other way... |
#34
| |||
| |||
|
|
"U3f" user exit on mvEnterprise does an "SP-ASSIGN" from Basic. |
![]() |
| Thread Tools | |
| Display Modes | |
| |