• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

Re: Automatic Printing on NT APP (Enterprise) Server

Re: Automatic Printing on NT APP (Enterprise) Server

<html><DIV>


Can you show us the syntax you are using in the runube batch file? What directory is the batch file located in on the APP server? How are you calling the RUNUBE batch file?
</P>


I was told by the JDE response line thatprinting RUNUBE jobs automatically did not work either but it does if you get everything set up right. We are sending mulitple jobs to multiple printers same as your requirement.</P>


Regards</P>


John
</P></DIV>
<DIV></DIV>
<DIV></DIV>>From: d vanvugt <D.VANVUGT@BENJAMINMOORE.CA>
<DIV></DIV>>Reply-To: jdelist@jdelist.com
<DIV></DIV>>To: jdelistml@jdelist.com
<DIV></DIV>>Subject: Automatic Printing on NT APP (Enterprise) Server
<DIV></DIV>>Date: Mon, 19 Feb 2001 13:00:13 -0800 (PST)
<DIV></DIV>>
<DIV></DIV>>Hi Folks,
<DIV></DIV>>
<DIV></DIV>>My searching shows that this has been discussed before, but I could not
<DIV></DIV>>find a resolution so I thought I'd try it again.
<DIV></DIV>>
<DIV></DIV>>Environment - OW B7321 SP12.3, AS/400 Enterprise server, NT App Server
<DIV></DIV>>
<DIV></DIV>>I would like to run UBE's on the App server by submitting them via
<DIV></DIV>>scheduled batch file with the RUNUBE command. Everything I've tried
<DIV></DIV>>thus far doesn't work - the job runs, the PDF is created in the
<DIV></DIV>>Printqueue, but it doesn't print. From a client with
<DIV></DIV>>PRINTIMMEDIATE=TRUE, I can submit a job to this server and it prints
<DIV></DIV>>automatically, no problem but it does not work from the RUNUBE command
<DIV></DIV>>on the server.
<DIV></DIV>>
<DIV></DIV>>I called JDE support, and was told that this did indeed not work, it was
<DIV></DIV>>a known problem which has "enhancement" status at this time.
<DIV></DIV>>
<DIV></DIV>>That being the case, I am wondering if anyone else has worked around
<DIV></DIV>>this issue in another way.
<DIV></DIV>>
<DIV></DIV>>JDE's suggestion was to try to automate the printing from the NT side,
<DIV></DIV>>using a batch file which would look for unprinted jobs and send them to
<DIV></DIV>>the printer. While my criteria is a bit more complicated than that due
<DIV></DIV>>to the need to send different jobs to different printers, I wonder if it
<DIV></DIV>>could be done.
<DIV></DIV>>
<DIV></DIV>>Acrobat has command-line options for printing, which I have tried and
<DIV></DIV>>had little success with so far.
<DIV></DIV>>
<DIV></DIV>>Any ideas anyone?
<DIV></DIV>>
<DIV></DIV>>Thanks,
<DIV></DIV>>
<DIV></DIV>>David Van Vugt
<DIV></DIV>>Network Support Analyst
<DIV></DIV>>Benjamin Moore & Co. Ltd.
<DIV></DIV>>Toronto, Ontario
<DIV></DIV>>d.vanvugt@benjaminmoore.ca
<DIV></DIV>>416-761-1436
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>--------------------------
<DIV></DIV>>To view this thread, visit the JDEList forum at:
<DIV></DIV>>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=5829
<DIV></DIV>>*************************************************************
<DIV></DIV>>This is the JDEList One World / XE Mailing List.
<DIV></DIV>>Archives and information on how to SUBSCRIBE, and
<DIV></DIV>>UNSUBSCRIBE can be found at http://www.JDELIST.com
<DIV></DIV>>*************************************************************
<DIV></DIV>>
<DIV></DIV><br clear=all><hr>Get your FREE download of MSN Explorer at http://explorer.msn.com
</p></html>
 

kf

Well Known Member
RE: Automatic Printing on NT APP (Enterprise) Server

maybe you should compare the job control records for a job submitted from
the command line, and for one submitted by a standard user. you may be able
to fudge it so that it thinks the job has been submitted from a client with
printimmediate set to true?
regards
kieran fitzgerald
 
AW: Automatic Printing on NT APP (Enterprise) Server

check out this:

sign on as ONEWORLD on your E-Server and start runube again.

-----Ursprungliche Nachricht-----
Von: kf [mailto:kf@srl.ie]
Gesendet: Dienstag, 20. Februar 2001 13:00
An: jdelistml@jdelist.com
Betreff: RE: Automatic Printing on NT APP (Enterprise) Server


maybe you should compare the job control records for a job submitted from
the command line, and for one submitted by a standard user. you may be able
to fudge it so that it thinks the job has been submitted from a client with
printimmediate set to true?
regards
kieran fitzgerald




--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=
5857
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 
RE: Automatic Printing on NT APP (Enterprise) Server

<html><DIV>


Printimmediate isn't used at all everything is controlled in the RUNUBE batch file - you just specify to print in the RUNUBE command and tell it what printer to send that job to go to:</P>


RUNUBEUSERNAMEPASSWORD PRD733 R55VERSION CSFG0001 QB7332 BATCH PRINT SAVE \\PRINTER</P>


We callthe RUNUBE batch file (which includes a line for each job we are processing) from a custom UBE that runs on the JDE scheduler. This stops us from having to use a 3rd party scheduler tocall theRUNUBE batch file although this would work exactly the same.</P>


Search on RUNUBE in the JDELIST archives - that is how came up with the info to get this working. Note for some reason you need the username and password to be in CAPS. Don't ask me why.</P>


Regards</P>


John</P>


</P>


</P>




</P></DIV>
<DIV></DIV>
<DIV></DIV>>From: kf <KF@SRL.IE>
<DIV></DIV>>Reply-To: jdelist@jdelist.com
<DIV></DIV>>To: jdelistml@jdelist.com
<DIV></DIV>>Subject: RE: Automatic Printing on NT APP (Enterprise) Server
<DIV></DIV>>Date: Tue, 20 Feb 2001 03:59:56 -0800 (PST)
<DIV></DIV>>
<DIV></DIV>>maybe you should compare the job control records for a job submitted from
<DIV></DIV>>the command line, and for one submitted by a standard user. you may be able
<DIV></DIV>>to fudge it so that it thinks the job has been submitted from a client with
<DIV></DIV>>printimmediate set to true?
<DIV></DIV>>regards
<DIV></DIV>>kieran fitzgerald
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>
<DIV></DIV>>--------------------------
<DIV></DIV>>To view this thread, visit the JDEList forum at:
<DIV></DIV>>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=5857
<DIV></DIV>>*************************************************************
<DIV></DIV>>This is the JDEList One World / XE Mailing List.
<DIV></DIV>>Archives and information on how to SUBSCRIBE, and
<DIV></DIV>>UNSUBSCRIBE can be found at http://www.JDELIST.com
<DIV></DIV>>*************************************************************
<DIV></DIV>>
<DIV></DIV><br clear=all><hr>Get your FREE download of MSN Explorer at http://explorer.msn.com
</p></html>
 

kf

Well Known Member
RE: Automatic Printing on NT APP (Enterprise) Server

another thing to check is the printer permission of the nt scheduler service
account. if it is set to localsystem (as is the default) then you wont be
able to connect to a network printer
regards
kieran fitzgerald
 

d_vanvugt

Member
RE: Automatic Printing on NT APP (Enterprise) Server

The syntax is as follows - actually, here's my batch file:

e:
cd oneworld\ddp\b7321\system\bin32
RUNUBE USERNAME PASSWORD CRPB732 R55PACK_N TEST QBATCH BATCH PRINT SAVE

The batch file is located in a folder called c:\batch.

I have tested this functionality by running the above RUNUBE command
directly from the command line, running the batch file by
double-clicking it, and running it from the NT Scheduler service. All
methods successfully submit and run the UBE, none print it. I'm testing
with my own Username and Password, which has full access to One World.
I'm logged on to the server with an account with administrative
privileges.

I have also tried running it INTERACTIVE, with the same results, and
have tried tacking the One World printer name on the end.

Any further insight is gratefully appreciated!

Thanks,

David Van Vugt
Network Support Analyst
Benjamin Moore & Co. Ltd.
Toronto, Ontario
d.vanvugt@benjaminmoore.ca
416-761-1436
 
Top