Printing issues with SCO UNIX v6.0.0 vs v5.0.7 and prior - SCO

This is a discussion on Printing issues with SCO UNIX v6.0.0 vs v5.0.7 and prior - SCO ; >I have a custom database application, written in CADOL, that previously worked FLAWLESSLY on versions of SCO, prior to v6.0.0 . It doesn't matter if I print directly to the HW port or via the spooler, the job either never ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Printing issues with SCO UNIX v6.0.0 vs v5.0.7 and prior

  1. Printing issues with SCO UNIX v6.0.0 vs v5.0.7 and prior

    >I have a custom database application, written in CADOL, that previously worked FLAWLESSLY on versions of SCO, prior to v6.0.0 . It doesn't matter if I print directly to the HW port or via the spooler, the job either never finishes or doesn't print at all. Jobs via the spooler, are actually worse than direct to port. I have included the ENV variables we use and also more info below.

    The ENV variables that are set up in the
    > .profile.
    >
    > DEV1=/usr/propac/printfile; export DEV1
    > DEV2=/dev/tty1a; export DEV2
    > PRINTER1=C0L0hplaser; export PRINTER1
    > PRINTER2=C0L0STD1096; export PRINTER2
    > hplaser=SPOOL; export hplaser
    > STD1096=022; export STD1096
    > STD1096_I=0002000; export STD1096_I
    > STD1096_O=; export STD1096_O
    > STD1096_C=004075; export STD1096_C
    > STD1096_L=; export STD1096_L
    >
    > These above statements set up 2 printers in our application. The
    > first is a networked Laser printer and the 2nd is a serial printer
    > hooked up to port tty1a, running 9600 baud with xon/xoff protocol.
    > In the application(character based), the user selects printer #1 or
    > #2 and off to the printer the job goes. Also, the hplaser printer is
    > defined and configured in the spooler using the scoadmin printers
    > utility. Nothing special there.
    > In v5.0.7, this works PERFECTLY. In v6.0.0mp3, it's a different
    > story. Jobs don't clear the spooler. Doing a lpstat -t, jobs get left
    > at the end(ie: hplaser-101 username ....) and it has to be
    > cancelled. What I am REAL suprised at, is going to Printer #2, it
    > will print like 1/2 the job and stop I think the main issue
    > here is "What is different in v6.0.0mp3?" I actually tried v6.0.0 and
    > I stepped thru each mp to see if the problem persisted in each, and it
    > did.


    Any ideas on what I could try??

    Thanks

  2. Re: Printing issues with SCO UNIX v6.0.0 vs v5.0.7 and prior

    On Fri, 13 Jun 2008, dccgary wrote:
    > >I have a custom database application, written in CADOL, that previously
    > >worked FLAWLESSLY on versions of SCO, prior to v6.0.0 . It doesn't
    > >matter if I print directly to the HW port or via the spooler, the job
    > >either never finishes or doesn't print at all. Jobs via the spooler,
    > >are actually worse than direct to port. I have included the ENV
    > >variables we use and also more info below.


    I have a few customers running cadol on OpenServer 6. We had to get an
    update licence and re-install cadol and then everything worked. My cadom
    programmer still makes changes to their application. I had to build a new
    binary on OpenServer 6, but that was about it.

    > The ENV variables that are set up in the
    > > .profile.
    > >
    > > DEV1=/usr/propac/printfile; export DEV1
    > > DEV2=/dev/tty1a; export DEV2
    > > PRINTER1=C0L0hplaser; export PRINTER1
    > > PRINTER2=C0L0STD1096; export PRINTER2
    > > hplaser=SPOOL; export hplaser
    > > STD1096=022; export STD1096
    > > STD1096_I=0002000; export STD1096_I
    > > STD1096_O=; export STD1096_O
    > > STD1096_C=004075; export STD1096_C
    > > STD1096_L=; export STD1096_L
    > >
    > > These above statements set up 2 printers in our application. The
    > > first is a networked Laser printer and the 2nd is a serial printer
    > > hooked up to port tty1a, running 9600 baud with xon/xoff protocol.
    > > In the application(character based), the user selects printer #1 or
    > > #2 and off to the printer the job goes. Also, the hplaser printer is
    > > defined and configured in the spooler using the scoadmin printers
    > > utility. Nothing special there.
    > > In v5.0.7, this works PERFECTLY. In v6.0.0mp3, it's a different
    > > story. Jobs don't clear the spooler. Doing a lpstat -t, jobs get left
    > > at the end(ie: hplaser-101 username ....) and it has to be
    > > cancelled. What I am REAL suprised at, is going to Printer #2, it
    > > will print like 1/2 the job and stop I think the main issue
    > > here is "What is different in v6.0.0mp3?" I actually tried v6.0.0 and
    > > I stepped thru each mp to see if the problem persisted in each, and it
    > > did.

    >
    > Any ideas on what I could try??


    I had to rebuild the cadol application running it on OpenServer 6 and then
    everything went well. We are at OpenServer 6 mp3. No problems. At the
    various locations, I have 5 network printers and 4 local. One location we
    move from serial printer's to Network printers. MB did did not come with
    any serial ports. We really need more information. Everything is working
    well.

    --
    Boyd Gerber
    ZENEZ 1042 East Fort Union #135, Midvale Utah 84047

  3. Re: Printing issues with SCO UNIX v6.0.0 vs v5.0.7 and prior

    On Jun 13, 10:11 am, Boyd Lynn Gerber wrote:
    > On Fri, 13 Jun 2008, dccgary wrote:
    > > >I have a custom database application, written in CADOL, that previously
    > > >worked FLAWLESSLY on versions of SCO, prior to v6.0.0 . It doesn't
    > > >matter if I print directly to the HW port or via the spooler, the job
    > > >either never finishes or doesn't print at all. Jobs via the spooler,
    > > >are actually worse than direct to port. I have included the ENV
    > > >variables we use and also more info below.

    >
    > I have a few customers running cadol on OpenServer 6. We had to get an
    > update licence and re-install cadol and then everything worked. My cadom
    > programmer still makes changes to their application. I had to build a new
    > binary on OpenServer 6, but that was about it.
    >
    >
    >
    > > The ENV variables that are set up in the
    > > > .profile.

    >
    > > > DEV1=/usr/propac/printfile; export DEV1
    > > > DEV2=/dev/tty1a; export DEV2
    > > > PRINTER1=C0L0hplaser; export PRINTER1
    > > > PRINTER2=C0L0STD1096; export PRINTER2
    > > > hplaser=SPOOL; export hplaser
    > > > STD1096=022; export STD1096
    > > > STD1096_I=0002000; export STD1096_I
    > > > STD1096_O=; export STD1096_O
    > > > STD1096_C=004075; export STD1096_C
    > > > STD1096_L=; export STD1096_L

    >
    > > > These above statements set up 2 printers in our application. The
    > > > first is a networked Laser printer and the 2nd is a serial printer
    > > > hooked up to port tty1a, running 9600 baud with xon/xoff protocol.
    > > > In the application(character based), the user selects printer #1 or
    > > > #2 and off to the printer the job goes. Also, the hplaser printer is
    > > > defined and configured in the spooler using the scoadmin printers
    > > > utility. Nothing special there.
    > > > In v5.0.7, this works PERFECTLY. In v6.0.0mp3, it's a different
    > > > story. Jobs don't clear the spooler. Doing a lpstat -t, jobs get left
    > > > at the end(ie: hplaser-101 username ....) and it has to be
    > > > cancelled. What I am REAL suprised at, is going to Printer #2, it
    > > > will print like 1/2 the job and stop I think the main issue
    > > > here is "What is different in v6.0.0mp3?" I actually tried v6.0.0 and
    > > > I stepped thru each mp to see if the problem persisted in each, and it
    > > > did.

    >
    > > Any ideas on what I could try??

    >
    > I had to rebuild the cadol application running it on OpenServer 6 and then
    > everything went well. We are at OpenServer 6 mp3. No problems. At the
    > various locations, I have 5 network printers and 4 local. One location we
    > move from serial printer's to Network printers. MB did did not come with
    > any serial ports. We really need more information. Everything is working
    > well.


    If you can't recompile, another way might be to use the ideas at
    http://aplawrence.com/SCOFAQ/FAQ_scotec7netdevice.html - that might
    work.



+ Reply to Thread