| |
Remote Printing Pre-formatting with Your Own Backend
So you want to pull a fast one on the spooler daemons? Why on earth would you
want to do that? Well, before you pass a print job off to the lpd or remote daemon,
you may want to have the output formatted with printer characteristics. The set up
can be done:
* Make sure you add the name and IP to the /etc/hosts file
*Create a remote queue (smit mkrque)
*Specify a queue name (pick a name)
*Specify destination host (make sure it is in /etc/hosts)
and also in /etc/hosts.lpd or /etc/hosts.equiv and /etc/hosts.lpd
*Specify the name of the queue (enter any name - it will be ignored)
*Specify name of device (pick name)
*cd /dev
*Touch any name as a que device (i.e., touch lplaser)
*smit mkvirprt
*Select printer attached to host
*Enter created device name (in this example lplaser)
*set up pcl, header, trailer, etc
*then exit out.
*type lsvirprt
*choose printer type (hplaserjet IIIsi)
*select your printer(lplaser)
*change attribute mo=qprt -P remotequename or
mo=/usr/local/bin/your script
Major Minor numbers for printers on 128 port,
transparent printing.
(.Printers attached to a terminal)
Create printer special file in /dev directory using the major number of the tty to which
the printer is attached, the minor number will be a different calculation.
The major number for the printer special file should be the same as the major number
of the tty special file. The minor number for the printer special should be equal to the
minor number for the tty special file plus 32768.
The name for the special printer file must be unique. The convention is to use
/dev/lpxN, where N is the number of the tty for the tty special file /dev/ttyN.
Example: The original tty number for tty 18 was
crw rw rw 1 root system 18,18 tty18
you would do mknod /dev/lpx18 c 18 32786
making the major number 18 and the minor number 32768 plus the minor number of
18, Chmod 666 lpx18. Set owner and group as required. Then create a virtual printer
as follows.
* smit mkvirprt
* select printer plotter attached to host
* Enter lpx18 as the device created above
* select ascii printer
* answer any additional field questions.
* Once the virtual printer is defined, you can do whatever
the manufacturer advised...
* Run the following command to set the terminal type where M
represents a terminal type like the ibm3151 and ttyN represents
the tty to which the printer is attached:
/usr/lbin/tty/stty-cxma term M tty18
* Then after each reboot
/usr/lbin/tty/stty-cxma tty18 onstr___ offstr___ to set
the pass thru parameters for a pc or modem.
.(like i.e mc5=^p^R and mc4=^P^T)
Local Queue Status Definitions:
READY: queue is ready, jobs will be sent to the printer
DOWN: Queue is stopped, jobs will be held. If qadm -U quename does not bring it
back up to READY, then there are problems. Some causes are, bad backend
programs, bad flags from front end, bad wiring, printer off line for more than the
time-out period.
DEV_BUSY: Device in use by other queue or program
DEV_WAIT: Printer off-line, out of paper, wires bad,etc. Will go to DOWN after
time-out when CTS low. CHECK CABLE. This can also occur when printer has
jammed, loose cable, or bad cable, or bad flow control.
OPR_WAIT: Waiting on operator action.
QUEUED: File queued and ready to be printed
RUNNING: Job is printing on this queue.
Terminal Server printing
First get the software that will make your life easier. .....We do not have stock in this
software, nor get any commission or anything.....but it does seem to work rather
well.
The product is called TCPrint.....you can visit laix software at their web site:
http://home.flash.net/~laixsoft/
It works with 3.2.x, 4.1.x and 4.x. and 5x There is a version that can be downloaded
as a trial.
* Generally you create a fake device in the /dev directory as above
touch /dev/lpa
* Add a print queue to the file /dev/lpa using SMIT
smit mkpq. Printer attached to a file (in the /dev/directory) Enter
the filename "lpa" (as above example) Enter your desired queue
names for the appropriate data streams(s)
*Change the backend program for this queue:
chquedev -q QNAME -d DNAME -a "file = FALSE" -a "backend =
/usr/lib/lpd/pio/etc/netprint program SERVER TCPORT LOGFILE" ..
(this is all one line .....even though it appears on three lines)
FALSE =the word FALSE in all uppercase letters...
QNAME= the print queue you
created via SMIT,
DNAME=is the queue device name (lpa above)
SERVER=the IP address of the print server box or hostname..
TCPPORT is the port number where the print server listens for incoming jobs or a
service name from the /etc/services file.
LOGFILE=is the file where you want all logging information to be placed. If you put
/dev/null in for the log filename, all logging information will be discarded.
HP Laser Jet attributes:
There are very few attributes that you can alter easily to make the HP LaserJet jump
through hoops. If you are changing the attributes for a virtual printer, the following is a
list of what can be changed easily:
-v line density 6,8
-w width 80,132
-p pitch 10,12,17
-l length 60 (default)
-z portrait/land +(landscape) !(portrait)
-s font Courier-bold
Although there are others that can be adjusted, major editing of the colon files are
required to accomplish it. /usr/sbin/chvirprt -q quename -d device -a w=80 substitute
your quename and device name above. the -a stands for attribute.
More
attributes of printers
splp
This can also be accomplished by going into smit, print spooling, programming tools
and doing the attribute directly. A great command to use with printers is the "splp"
command. This allows you to temporarily change some characteristics on the fly. It
is similar to the stty command.
REMEMBER
that these changes will not be kept after a reboot. It is also important to note that
most of these settings are not applicable to printing using the AIX print commands.
However, these settings can be very useful for changing parameters when "catting"
files to a device, or when doing diagnostics. splp -p+ lp0. This will set the driver to
passthrough mode. When you cat a file (i.e. cat filename > /dev/lp0 ). You can check
to see if the printer picked up any escape sequences for formatting.
Another common problem is excessive form feeds, which we sometimes remove
with the -f! Remember that the splp command is a troubleshooting tool to help you
rule out baud rate, cable, etc.
Printing to a /dev/tty# device Remember it requires DCD (unless CLOCAL is set) If
printer is taken off-line during periods of inactivity, and job is sent a file, and the
printer is off-line, the data will be lost and never reach the printer. This is because
XOFF is not seen unless the port is open. When adding a printer device, the constant
requirement is that CTS must be asserted for the RISC to send data. IF CTS does
not receive a signal from somewhere, you will get queues that go down. Attempts to
cat a file to the device will hang and eventually give an error. The desired cable will
have CTS receive its signal from the printer RTS signal. Sometimes people skrimp
and use 3 or 4 wire cables. When this is done, the RTS signal from the computer can
be wrapped back to the CTS signal. The other critical lines are the data lines. TxD
from the printer must go to RxD of the computer and vice versa. TxD sends data to
RxD. For hardware flow control, the signal for flow control on the printer must be tied
to DCD on the AIX system. Also some printers require certain signals like DSR
before they will print.
Migrating printers to another machine
Here are the instructions I received from IBM. NOTE: Be advised that IBM claims
they do not support this through IBM.
Migrating Print Queues:
1. copy the /etc/qconfig (make a copy of the original before)
2. Copy the following files:
/var/spool/lpd/pio/@local/custom files
/var/spool/lpd/pio/@local/dev files
/var/spool/lpd/pio/@local/ddi files
3. change the permissions on the copied files to 664 chmod 664 filename
4. redigest the queue's
enq -d
5. run the chvirprt command on each queue
chvirprt -q -d
Note; If you have a lot of queues, the best thing is to create a short script to do this
for you. I grab the queue name and device name by running lsallq -c and saving it to a
file.
6. cycle the printer subsystem
stopsrc -cg spooler
startsrc -g spooler
So only Root can print?
There are a lot of tips for printing. The most important are permissions and
space. Always check the space with the df command. If /tmp or /var are filled,
you will have printing problems. Next you need to check permissions.
How easy it is for someone who is well meaning to change a permission on a
directory or a file.
File Permissions, Owners and Groups
Path is for that version first instead of the real version..........
which lp should produce /usr/bin/lp
which enq should also produce /usr/bin/enq
Sometimes an update to a third party software will change the permissions of
/ with the owner and group. Or put another shell program for lp. Look for it with
the which command. Also try printing with lp and enq and see if one works
and the other doesn't.
At minimum the following should be checked. This is especially true if only
root user (superuser) can print:
-r-sr-s--- 1 root printq 58989 Oct 26 1994 /usr/sbin/qdaemon
-r-sr-s--- 1 root printq 50099 Oct 26 1994 /usr/sbin/lpd
-r-sr-sr-x 1 root printq 59262 Oct 26 1994 /bin/enq
-r-xr-xr-x 1 bin bin 31493 Oct 26 1994 /bin/qprt
-r-xr-xr-x 1 bin bin 30397 Oct 26 1994 /bin/lp
-r-xr-xr-x 1 bin bin 31421 Oct 26 1994 /bin/lpr
-r-xr-xr-x 1 bin bin 30909 Oct 26 1994 /bin/lpstat
-r-xr-sr-x 1 bin printq 54633 Oct 13 1994 /usr/lib/lpd/piobe
-r-sr-x--- 1 root printq 38205 Oct 26 1994 /usr/lib/lpd/digest
-r-sr-x--- 1 root printq 52088 Oct 26 1994 /usr/lib/lpd/qstatus
-r-sr-xr-x 1 root printq 49626 Aug 14 1995 /usr/lib/lpd/pio/etc/pioout
crw-rw-rw- 1 root system 2, 2 Jul 09 08:56 /dev/null
-rw-rw-r-- 1 root printq 6198 Sep 27 10:55 /etc/qconfig
More to check but you may not have all of them, based on what you installed.
:/usr/lib/lpd/pio/etc
r--r--r-- 1 root printq 741 Jul 27 1994 ascii.attach
-r-xr-xr-x 1 bin bin 557 Nov 11 1994 bull.head
-r-xr-xr-x 1 bin bin 1037 Nov 11 1994 bull.header
-r-xr-xr-x 1 bin bin 390 Nov 11 1994 bull.trail
-r-xr-xr-x 1 bin bin 732 Nov 11 1994 bull.trailer
-r-xr-xr-x 1 bin bin 1081 Nov 11 1994 bullps.header
-r-xr-xr-x 1 bin bin 938 Nov 11 1994 bullps.trailer
-rw-rw-r-- 1 root printq 18990 Jan 26 1994 codepage.txt
-r--r--r-- 1 root printq 736 Jul 27 1994 file.attach
-r--r--r-- 1 root printq 767 Feb 6 1997 hpJetDirect.attach
-r--r--r-- 1 root printq 779 Jul 27 1994 local.attach
-r--r--r-- 1 root printq 935 Sep 16 1994 mbcs.tbl
-r--r--r-- 1 root printq 3646 Aug 30 1994 nls.dir
-r--r--r-- 1 root printq 49288 Mar 20 1996 pioattr1.cat
-r--r--r-- 1 root printq 61196 Aug 27 1994 piobe.cat
-r-xr-xr-x 1 bin bin 15038 Jan 6 1996 pioburst
-r-xr-xr-x 1 bin bin 52286 Jan 6 1996 piocfapi
-r-xr-xr-x 1 bin bin 11800 Jan 6 1996 piochdfq
-r-xr-xr-x 1 bin bin 4062 Nov 11 1994 piochpq
-r-xr-x--- 1 root printq 9239 Nov 11 1994 piodmgr
-r-sr-sr-x 1 root printq 2890 Jan 6 1996 piodmgrsu
-r-xr-xr-x 1 bin bin 47778 Jan 6 1996 pioevattr
-r-xr-xr-x 1 bin bin 54492 Feb 26 1996 pioformat
-r-xr-xr-x 1 bin bin 1626 Jan 22 1995 piofquote
-r-xr-xr-x 1 root printq 22998 Jun 1 1996 piohpnpf
-r-xr-xr-x 1 bin bin 589 Nov 11 1994 pioinit
-r-xr-xr-x 1 root printq 618 Nov 11 1994 piojetd
-r-xr-xr-x 1 bin bin 5199 Nov 11 1994 piolpx
-r-xr-xr-x 1 bin bin 18164 Jan 6 1996 piolspt
-r-xr-xr-x 1 bin bin 40754 Jan 6 1996 piolsvp
-r-xr-xr-x 1 bin bin 13396 Jan 6 1996 piomgpdev
-r-xr-xr-x 1 bin bin 11757 Apr 30 1996 piomisc_ext
-r-xr-sr-x 1 root printq 39014 Jan 6 1996 piomkapqd
-r-xr-xr-x 1 root printq 4733 Mar 22 1995 piomkjetd
-r-sr-x--- 1 root printq 33736 Jan 6 1996 piomkpq
-r-xr-xr-x 1 bin bin 8774 Jan 6 1996 piomsg
-r-sr-xr-x 1 root printq 49570 May 30 1996 pioout
-r-xr-xr-x 1 bin bin 9654 Jan 26 1994 pioqms100
-r-xr-xr-x 1 bin bin 4288 Nov 11 1994 piorlfb
-r--r--r-- 1 root printq 1819 Aug 27 1994 piosplp.cat
-r--r--r-- 1 root printq 19153 Jul 27 1994 printers.inv
-r--r--r-- 1 root printq 684 Jul 27 1994 remote.attach
r-s r-s - - 1 root printq 58989 /usr/sbin/qdaemon
r-s r-s - - 1 root printq 50099 /usr/sbin/lpd
r-s r-s r-x 1 root printq /bin/enq
r-x r-x r-x 1 bin bin /bin/qprt
r-x r-x r-x 1 bin bin /bin/lp
r-x r-x- r-x 1 bin bin /bin/lpr
r-x r-x r-x 1 bin bin /bin/lpstat
/usr/lib/lpd
-r-xr-sr-x 1 bin printq 80036 Feb 26 1996 piobe
-r-xr-xr-x 1 bin bin 17254 Jun 25 1996 plotgbe
-r-xr-xr-x 1 root printq 14450 Apr 9 1995 plotlbe
-r-sr-x--- 1 root printq 53266 Jul 20 1996 qstatus
-r-sr-x--- 1 root printq 50280 Sep 10 1996 rembak
-r-sr-x--- 1 root printq 39178 Jun 13 1996 digest
lrwxrwxrwx 1 root printq 13 Oct 17 2025 lpd -> /usr/sbin/lpd
drwxrwxr-x 9 root printq 512 Feb 6 1997 pio
r-s r-x r-x 1 root printq /usr/lib/lpd/pio/etc/pioout
crw-rw-rw 1 root system /dev/null
rw- rw-r-- 1 root printq /etc/qconfig
rw rw - - 1 root printq /etc/qconfig.bin
drwxr-xr-x bin bin /
drwxrwxr-x bin bin /var
drwxrwxr-x bin bin /var/spool
drwxrwxr-x bin printq /var/spool/lpd
drwxrwxr-x root printq /var/spool/lpd/qdir
drwxrwxr-x root printq /var/spool/lpd/stat
drwxrwxr-x bin printq /var/spool/qdaemon
drwxr-xr-x bin bin /usr
drwxr-xr-x bin bin /usr/bin
drwxr-xr-x bin bin /usr/sbin
drwxrwxr-x root system /etc
-rw-rw-r-- root system /etc/hosts
drwxrwsrwt bin bin /tmp
To check directories use:
ls -ld
For example, ls -ld / would return information for root directory, and ls -ld /etc
would return information for the etc directory.
If you are not seeing all the printer menus,
do a lslpp -l | grep printers.rte and
lslpp -l | grep bos.rte.printers. If the filesets are not installed, you will not have all
the printer menus. See the other sheet on Printer Smit Menus on this site.
Remote Printer Checklist
Check the following items for the host acting as the remote print server:
Make sure that all client machines (foreign hosts) are listed in the
etc/hosts.lpd file.
Make sure that the TCP/IP subsystem is running.
Check for the existence of the /usr/spool/lpd directory.
Make sure that the /etc/locks/lpd directory does not exist if the lpd daemon is
not running.
Make sure that both the lpd daemon and the qdaemon are running.
Clean the print ques often. See the additional sheet on this web site.
Remember to stopsrc -cg spooler and then startsrc -g spooler when you are
done cleaning.
Verify that the queue name and server name for the remote print server are
correct in the /etc/qconfig file.
Timeout of Printers, what to do?
If the queue is defined as a remote printer with standard processing (backend
is rembak), adding -T60 to the backend line in /etc/qonfig may help. If the
queue is remote with local filtering, then -T60 can be put into the rembak flags
section of /usr/lib/lpd/pio/etc/piorlfb. If the queue is defined using the HP
Jetdirect software (piojetd backend), then -T60 doesn't apply.
lp0:
host = hostname
s_statfilter = /usr/lpd/aixshort
l_statfilter = /usr/lpd/aixlong
rq = queuename
device = dlp0
dlp0:
backend = /usr/lpd/rembak -T99
cp /usr/lib/lpd/pio/etc/piorlfb
/usr/lib/lpd/pio/etc/piorlfb.orig
# vi /usr/lib/lpd/pio/etc/piorlfb
typeset piorlfb_rbflags="-T99" #rembak flags
NO guarantee wakeup down printer daemon
Can be Added to cron to reset down print ques every so many minutes. Probably
best to do every 1/2 hours
-----------------------
#!/bin/ksh
#
#
THISHOST=`uname -n`
lpstat|grep DOWN|awk '{print $1}' >> /tmp/lpstatdown.log
if test -s /tmp/lpstatdown.log
then
for i in `cat /tmp/lpstatdown.log`
do
enable $i
done
echo "The date/time is `date` " >> /tmp/lpstatdown.log
echo "\nThese queues were DOWN and have been enabled." >>
/tmp/lpstatdown.log
mail -s "$THISHOST Printer Status" root@localhost < /tmp/lpstatdown.log
sleep 5
rm -f /tmp/lpstatdown.log
fi
Preventing extra form feeds
lsvirprt
Select queue
_Z=!
Printer messages
Use lsvirprt to look at the virtual printer. The _A setting
can be used to determine if messages go to the console, or the submitter's
mail. There is another attribute called "user to receive intervention messages"
which I don't recall the attribute name for, but you can set it to "nobody" and
the messages will be sent to /dev/null. lsvirprt;_ A=0
or
lsvirprt; si = nobody
or
lpr.* /dev/null in /etc/syslog.conf; refresh -s syslogd
or
use a tty driver (w/ Xon/Xoff flow ctrl) instead of an lp driver
MESSAGES
A. Backend generated
1) Intervention required (e.g., printer out of paper). Sent to submitter of job.
Controlled by virtual printer _si attribute (users, separated by commas, to get
intervention messages; null string is job submitter), e.g., si=nobody.
2) Backend error messages (e.g., use of invalid flag). Controlled by the virtual
printer _A attribute, e.g., A=0
Additional port problem
There is a known problem with 4.2.1 and 4.3.2 that it sends the information
too quickly out the serial ports for most printers to handle. They suggest that
DTR or hardware flow be used.....but even that may cause an overrun of data.
One additional thing to try, besides lowering the baud rate, is to change the
transmit buffer count on the port......you can also decrease the baud rate on
your printers
If it is the native serial port you can go into smit, devices, printer plotter and
change it there or if on 128 or 64 port .here is command line (default is 16 for
the tbc16 count)
chdev -l 'lp1' -w 'portnumber' -a tbc16='4'
Other things to try if you cannot get a printer to print.
cat file > /dev/lp# and get any useful info? When AIX opens the serial port, it
raises DTR and RTS and expects CTS and DCD coming back from the
printer.
Another trick instead of an lp, define a tty on the port instead. Try cat file >
/dev/tty# and see if that works. The tty driver doesn't care about CTS (unless
RTS/CTS flow control is used) and thus you can sometimes get by with
cabling that doesn't work for an lp.
splp /dev/lp0
This is somewhat the equivalent of stty for the tty subsystem. If allows simple
changes to printer device driver parameters. These changes are not kept after
a reboot
You can issue splp -p+ /dev/lp0 to add passthrough mode and the splp
command allows other changes as well.
Example: splp -l 88 -w 132 -i 5 lp2
PRINTER SMIT MENUS A PROBLEM
Error 0782-626,
0732-346 odm not able to open sm_cmd_hdr or
1820-037 or even sometimes
1800-109 or 1800-106
It may mean that you need to load a printer
driver for a particular printer...or ...............
You were dialed in to a machine, trying to change a printer, and it
disconnected or hung on you.The database information got corrupted....The
smit printer menu files are not there, or they are of zero byte size, or have
today's date. or..... You have a broken bos.rte.printers, or printers.rte
First,
cd /var/spool/lpd/pio/@local/smit
and do an ls -la
Do you have sm_cmd_hdr? Is it zero bytes?
Today's date?
If so do a lslpp -l | grep printers.rte Is it loaded? Broken? Committed?
lppchk -v and lppchk -c?
If the lslpp command did not show printers.rte as being loaded, load it. If it is
broken you can do a force overwrite or load a newer patch level of the
fileset...but be sure you have done a mksysb first, in case you have to
restore...and make sure you have an old mksysb...in case you have to reload
it again.....
You can delete the files in the /var/spool/lpd/pio/@local/smit and restore from
an old mksysb (just those files...) or do a mv to another name (mv
sm_cmd_hdr sm_cmd_hdr.old) so they do not exist in that directory BEFORE
you restore.
Remember you may have already corrupted other information as well.
Perhaps the /etc/qconfig file which contains all your printers. If you restore the
printers.rte, you printer definitions may have to be redone for ALL your
printers.....You may be lucky and all will be well..but there is no guarantee.
Here are the approximate sizes for my files:
Remember these can vary on a lot of systems based on what you have
loaded. But if they are zero in size, you will need to restore the values.
/var/spool/lpd/pio/@local/smit
drwxrwxr-x 2 root printq 512 Jan 05 15:43 .
drwxrwxr-x 7 root printq 512 Jan 05 15:43 ..
-rw-rw-r-- 1 root printq 8192 Mar 18 08:52 sm_cmd_hdr
-rw-rw-r-- 1 root printq 4096 Mar 18 08:52 sm_cmd_hdr.vc
-rw-rw-r-- 1 root printq 4096 Mar 18 08:52 sm_cmd_opt -
-rw-rw-r-- 1 root printq 4096 Mar 18 08:52 sm_cmd_opt.vc
-rw-rw-r-- 1 root printq 4096 Jan 05 15:43 sm_menu_opt
-rw-rw-r-- 1 root printq 4096 Jan 05 15:43 sm_menu_opt.vc
-rw-rw-r-- 1 root printq 4096 Jan 05 15:43 sm_name_hdr
-rw-rw-r-- 1 root printq 4096 Jan 05 15:43 sm_name_hdr.vc
On some machines you can find an original copy in:
/usr/lpp/printers.rte/inst_root/var/spool/lpd/pio/@local/smit/
do a find on your system to see if they are there and at the right size.
Some times when the printer menus are gone you can simply copy the
sm_(filenames) from the original directory. However, new changes and
additions may be missing.
cp /usr/lpp/printers.rte/inst_root/var/spool/lpd/pio/@local/smit/*
/var/spool/lpd/pio/@local/smit/
Then stop the printers
stopsrc -cg spooler and then
startsrc -g spooler
and all could be well....
Sometime you will need to run this script.
-------------------------
Before running this script, check and see if it is fixed first!
Then issue the following commands:
for FILE in `ls /var/spool/lpd/pio/@local/custom`
do
/usr/lib/lpd/pio/etc/piodigest $FILE
done
Then stop and start printers and try it....
OR THIS ONE:
put the following in a file and chmod 777 on it.
#!/bin/ksh
cd /var/spool/lpd/pio/@local/custom
for file in `ls`
do
QNAME=`echo $file | cut -d':' -f1`
DEVICE=`echo $file| cut
Changed your host name?
I also saw a similar problem and a similar error message. It turned out that
when we renamed our host, it was not renamed in the smit files. For local
host, it had our old host name . You could create a link (not the best way) to
@local to what it should be
<#link @local newhostname>
ls -la the /var/spool/lpd/pio:
newhostname -> /var/spool/lpd/pio/@local
You still may have to run the following:
for FILE in `ls /var/spool/lpd/pio/@local/custom`
do
/usr/lib/lpd/pio/etc/piodigest $FILE
done
Maybe the system smit menus are messed up?
If that doesn't fix the problem, check this directory:
NOW REMEMBER THESE ARE not the same files as before. Do not copy
form the inst_root directory......you must use mksysb. to restore these.. or
from a saved directory copy you made in advance.
/usr/lib/objrepos
-rw-rw-r-- 1 root system 172032 Apr 22 12:29 sm_cmd_hdr
-rw-rw-r-- 1 root system 376832 Apr 22 12:29 sm_cmd_hdr.vc
-rw-rw-r-- 1 root system 749568 Apr 22 12:29 sm_cmd_opt
-rw-rw-r-- 1 root system 356352 Apr 22 12:29 sm_cmd_opt.vc
-rw-rw-r-- 1 root system 327680 Apr 22 12:35 sm_menu_opt
-rw-rw-r-- 1 root system 61440 Apr 22 12:35 sm_menu_opt.vc
-rw-rw-r-- 1 root system 102400 Apr 22 sm_name_hdr
If any of these are zero bytes, you will need to restore them from a
mksysb.....
Restore the files or directories by running the following commands:
cd / (if the file is to be restored to its original place)
tctl -f /dev/rmt# rewind
restore -s4 -xqdvf /dev/rmt#.1 ./dir/filename for one file)
OR
restore -s4 -xqdvf /dev/rmt#.1 ./dir (for all files in directory)
Other Useful Information:
Parallel Printer Info
LPD/LPR Sheet
Frequent Error Messages
Clearing Print Que
FAQ printer
serial flow control
Serial Printers
Wake UP HPLJ5
128 port cables for printers
(slg 3/2002)
|
