Sponsored Content
Operating Systems AIX How do I set up a Zebra Printer on AIX? Post 303036732 by bakunin on Tuesday 9th of July 2019 03:24:08 PM
Old 07-09-2019
Quote:
Originally Posted by DLooney
How would I create a driver myself?
Actually a good question! search the net for the piobe and the rembak commands. piobe is the print job manager program, the rembak sends the job to the print server. rembak is a shell script and you can do all sorts of manipulations to the data stream to be sent inside it before actually sending it. Now you need to find out about the printers control sequences (perhaps in the printer documentation) and you can build your own post-processor for this specific printer.

Be warned, though: how you do it is - see above - simple to explain but that doesn't mean it is easy to accomplish. It is probably a tedious task and you might be cheaper off overall if you just buy a new printer. On the other hand i did that once ~25 years ago and learned a lot about the AIX printing system. Experience like this is a absolutely excellent learning experience, so if you want to try it: more power to you!

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

set up HP printer in Sun Solaris 2.8

Is there any documentation as to how to set up/register a printer in Sun Solaris server? Thanks in advance. (1 Reply)
Discussion started by: simt
1 Replies

2. Solaris

Printer set and format?

I have a network printer LaserJet 4050N on Sun Solaris Sun-Fire-408R. When I lp text.lis, it printed out steps like indent lines. When I unix2dos test.lis, it print out all right. I tried to print a report from Banner Finance - FGRCTRL, and chose the the same printer with command line: ... (2 Replies)
Discussion started by: simt
2 Replies

3. UNIX for Advanced & Expert Users

How to set up dummy printer on UNIX

Hi, I work at IT department of a home furnishing company in Canada. Presently we are working on printer issue on UNIX system and we like to set up a dummy printer on the system. We are not much sure about the procedure to try it and it woul dbe great if we get some advice to go ahead. Thanks... (3 Replies)
Discussion started by: srabanti
3 Replies

4. AIX

Can you set up a networked printer as a local print queue?

Fairly simple question, I think. Still trying to get my head around AIX print queues. Most of our problems seem to stem from print queues going down. This generates help-desk calls when users call up to get their queues started or to get rid of the emails that qdaemon sends them. Looking at... (0 Replies)
Discussion started by: alexop
0 Replies

5. AIX

Unable to set remote printer in AIX

Hi all, I am a beginner in AIX. I am facing a problem with remote printing in AIX. HP laser jet 1320 printer is connected to a printer server (PCI Mini - 100U3), which is configured as remote printer from AIX server. But I am not able to print from the AIX server by using "lp -d... (0 Replies)
Discussion started by: Rainy
0 Replies

6. Solaris

Trying to add Zebra label printer in Solaris 9

I talked to Zebra, but they told me that they only support adding printer to Windows environment. They did sent me a link to a document which describes how to set up a print queue on a Sun Solaris system for Zebra Print Server. ... (1 Reply)
Discussion started by: agarcia19
1 Replies

7. SCO

How to set up a printer on SCO 5

1. Does all the man pr commands work as expected on SCO 5? 2. Do I have to do some special printer setup to connect the printer to the server before trying to print? Thanks - Much. (1 Reply)
Discussion started by: ggats11
1 Replies

8. AIX

Zebra printing in AIX

I have a Zebra QL420plus that when I print to it, it prints blank page. It is setup as Generic ASCII port 9100. I saw info about sending a .asc file to it before any print. Anyone have this info? (1 Reply)
Discussion started by: mcmc92
1 Replies

9. AIX

Will it affect my AIX LPAR security, when i set up email alerts on AIX server.

Hello, I've set up email alerts on AIX Servers. so that i can get email notifications (via mail relay server) when ever there is abnormal behavior. for example 1) my script monitors CPU/disk/memory etc... when it reaches high water ark, it will send an email alert. 2) disk usage alerts 3)... (5 Replies)
Discussion started by: System Admin 77
5 Replies

10. Solaris

HOW To configure the ZEBRA printer on Solaris?

Hi Guys, How to configure the ZEBRA printer on Solaris . only below information is provided. like how it should appear in printers.conf and IP to add in hosts file. In printers.conf: super_exp_zex2et9x:\ :bsdaddr=server1,super_exp_zex2et9x,Solaris: super_exp_zex2et1x:\... (1 Reply)
Discussion started by: manalisharmabe
1 Replies
ICON(1) 						      General Commands Manual							   ICON(1)

NAME
icon - interpret or compile Icon programs SYNOPSIS
icont [ option ... ] file ... [ -x arg ... ] iconc [ option ... ] file ... [ -x arg ... ] DESCRIPTION
icont and iconc each convert an Icon source program into executable form. icont translates quickly and provides interpretive execution. iconc takes longer to compile but produces programs that execute faster. icont and iconc for the most part can be used interchangeably. This manual page describes both icont and iconc. Where there there are differences in usage between icont and iconc, these are noted. File Names: Files whose names end in .icn are assumed to be Icon source files. The .icn suffix may be omitted; if it is not present, it is supplied. The character - can be used to indicate an Icon source file given in standard input. Several source files can be given on the same command line; if so, they are combined to produce a single program. The name of the executable file is the base name of the first input file, formed by deleting the suffix, if present. stdin is used for source programs given in standard input. Processing: As noted in the synopsis above, icont and iconc accept options followed by file names, optionally followed by -x and arguments. If -x is given, the program is executed automatically and any following arguments are passed to it. icont: The processing performed by icont consists of two phases: translation and linking. During translation, each Icon source file is translated into an intermediate language called ucode. Two ucode files are produced for each source file, with base names from the source file and suffixes .u1 and .u2. During linking, the one or more pairs of ucode files are combined to produce a single icode file. The ucode files are deleted after the icode file is created. Processing by icont can be terminated after translation by the -c option. In this case, the ucode files are not deleted. The names of .u1 files from previous translations can be given on the icont command line. These files and the corresponding .u2 files are included in the linking phase after the translation of any source files. The suffix .u can be used in place of .u1; in this case the 1 is supplied auto- matically. Ucode files that are explicitly named are not deleted. iconc: The processing performed by iconc consists of two phases: code generation and compilation and linking. The code generation phase produces C code, consisting of a .c and a .h file, with the base name of the first source file. These files are then compiled and linked to produce an executable binary file. The C files normally are deleted after compilation and linking. Processing by iconc can be terminated after code generation by the -c option. In this case, the C files are not deleted. OPTIONS
The following options are recognized by icont and iconc: -c Stop after producing intermediate files and do not delete them. -e file Redirect standard error output to file. -f s Enable full string invocation. -o name Name the output file name. -s Suppress informative messages. Normally, both informative messages and error messages are sent to standard error output. -t Arrange for &trace to have an initial value of -1 when the program is executed and for iconc enable debugging features. -u Issue warning messages for undeclared identifiers in the program. -v i Set verbosity level of informative messages to i -E Direct the results of preprocessing to standard output and inhibit further processing. The following additional options are recognized by iconc: -f string Enable features as indicated by the letters in string: a all, equivalent to delns d enable debugging features: display(), name(), variable(), error trace back, and the effect of -f n (see below) e enable error conversion l enable large-integer arithmetic n produce code that keeps track of line numbers and file names in the source code s enable full string invocation -n string Disable specific optimizations. These are indicated by the letters in string: a all, equivalent to cest c control flow optimizations other than switch statement optimizations e expand operations in-line when reasonable (keywords are always put in-line) s optimize switch statements associated with operation invocations t type inference -p arg Pass arg on to the C compiler used by iconc -r path Use the run-time system at path, which must end with a slash. -C prg Have iconc use the C compiler given by prg ENVIRONMENT VARIABLES
When an Icon program is executed, several environment variables are examined to determine certain execution parameters. Values in paren- theses are the default values. BLKSIZE (500000) The initial size of the allocated block region, in bytes. COEXPSIZE (2000) The size, in words, of each co-expression block. DBLIST The location of data bases for iconc to search before the standard one. The value of DBLIST should be a blank-separated string of the form p1 p2 ... pn where the pi name directories. ICONCORE If set, a core dump is produced for error termination. ICONX The location of iconx, the executor for icode files, is built into an icode file when it is produced. This location can be overridden by setting the environment variable ICONX. If ICONX is set, its value is used in place of the location built into the icode file. IPATH The location of ucode files specified in link declarations for icont. IPATH is a blank-separated list of directories. The current directory is always searched first, regardless of the value of IPATH. LPATH The location of source files specified in preprocessor $include directives and in link declarations for iconc. LPATH is otherwise sim- ilar to IPATH. MSTKSIZE (10000) The size, in words, of the main interpreter stack for icont. NOERRBUF By default, &errout is buffered. If this variable is set, &errout is not buffered. QLSIZE (5000) The size, in bytes, of the region used for pointers to strings during garbage collection. STRSIZE (500000) The initial size of the string space, in bytes. TRACE The initial value of &trace. If this variable has a value, it overrides the translation-time -t option. FILES
icont Icon translator iconc Icon compiler iconx Icon executor SEE ALSO
The Icon Programming Language, Ralph E. Griswold and Madge T. Griswold, Prentice-Hall Inc., Englewood Cliffs, New Jersey, Second Edition, 1990. Version 9.1 of Icon, Ralph E. Griswold, Clinton L. Jeffery, and Gregg M. Townsend, IPD267, Department of Computer Science, The University of Arizona, 1995. Version 9 of the Icon Compiler, Ralph E. Griswold, IPD237, Department of Computer Science, The University of Arizona, 1995. icon_vt(1) LIMITATIONS AND BUGS
The icode files for the interpreter do not stand alone; the Icon run-time system (iconx) must be present. Stack overflow is checked using a heuristic that is not always effective. 1 November 1995 IPD244b ICON(1)
All times are GMT -4. The time now is 08:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy