[Info-vax] Xerox Phaser 6500N and DCPS issues.

[Carl Friedberg]

Hi Paul,

I still have not tested. Here is a sample of what I have so far. For the
second printer I removed all of the comments to debug a DCL error message
(too many arguments).

$   write sys$output "Starting Xerox Phaser 6500 LaserPSX on Queue PSX"
$   DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$PSX_PRODUCT_NAME "HPGENERIC"
$   IF .NOT. SETUP_MODE THEN @SYS$STARTUP:DCPS$EXECUTION_QUEUE -
        psx -                           ! P1 - Execution queue name
        "IP_RAWTCP/laserpsx.example.com:9100" - ! P2 - printserver node name
        DCPS_LIB -                      ! P3 - Logical name for library(ies)
        "" -                            ! P4 - Default queue parameters

"/default=(form=dcps$default,feed)/separate=(NOFLAG,NOBURST,NOTRAILER)" -
        "" -                            ! P6 - Communication speed
        "" -                            ! P7 - Device characteristics
        ""                              ! P8 - Verify on/off
$!
$!
$   write sys$output "Starting Xerox Phaser 6500 LaserPSY on Queue PSY"
$   DEFINE /EXECUTIVE_MODE /SYSTEM DCPS$PSY_PRODUCT_NAME "HPGENERIC"
$   IF .NOT. SETUP_MODE
$     THEN
$       @SYS$STARTUP:DCPS$EXECUTION_QUEUE psy -"IP_RAWTCP/
laserpsy.example.com:9100" DCPS_LIB "" -

"/default=(form=dcps$default,feed)/separate=(NOFLAG,NOBURST,NOTRAILER)" ""
"" ""
$     endif

Do you have any suggestions (the TCPIP pirnters run on Multinet).

What is the best way to handle a multi-architecture (AXP/I64) cluster. Is
this done by DCPS (processor qualifier?) The DCPS$STARTUP procedure doesn't
bother queues that are already running, so it seems to do OK, but I worry
about situations like this where there are different executable images
involved on the different architectures.

Later today I will report on how it is running based on i64 architecture.
On AXP I saw the same errors as Jan-Eric reported, if I remember correctly.

Thanks,

Carl

On Wed, Mar 11, 2015 at 9:43 PM, Paul Anderson via Info-vax <
info-vax at rbnsn.com> wrote:

> In article <mdmhoi$f1k$1 at news.albasani.net>, Jan-Erik Soderholm
> <jan-erik.soderholm at telia.com> wrote:
>
> > Jan-Erik Soderholm skrev den 2015-03-06 13:38:
> >
> > I think I wrote earlier that the printer didn't print
> > anything at all. Now, with another guy on-site, it seems
> > as that was wrong. The operator had simply tossed the
> > error-printout and said that "nothing was printed"... :-)
> >
> > Here is a copy of what actualy *is* printed:
> > http://jescab2.dyndns.org/pub_docs/wp_20150310_10_26_18_pro.jpg
>
> So the 6500 chokes on the PostScript 'duplexmode' command.  Seems to me
> some other printers have done this in the past.  Have to check on that.
> I also wonder what '/e@#q!3&' is doing on the stack.
>
> Do you have the DCPS$queue_PRODUCT_NAME logical name defined?
>
> Paul
> _______________________________________________
> Info-vax mailing list
> Info-vax at rbnsn.com
> http://rbnsn.com/mailman/listinfo/info-vax_rbnsn.com
>