In B7331, the setting is in the JDE client's workstation jde.ini which comes
from the deployment server. The setting is PrintImmediate=FALSE by default.
To enable Print Immediate, set PrintImmediate=TRUE. The setting affects all
UBEs initiated from the workstation.
Chi Lee
B7331 SP11.3, NT4.0 server and Win2000 clients, SQL Server 7.0, Citrix
Win2000
I may not have made this clear... I mean for an individual execution of a
UBE, is it stored somewhere whether or not Print Immediate was on for that
execution?
---
From: rfletche [mailto:rfletche@bru-hub.dhl.com]
Sent: Wednesday, October 31, 2001 11:32 AM
To: Scotti Whitmire
Subject: Re: Print immediate stored?...
I think I understand what you are asking... Is there a file containing the history of a submitted job? I don't think that there is unless you have logging turned on and even then, the information will not be easily attained.
The only place that I can think of is F986110 (Job
Control Status Master) in the Server Map but I don't
see anything in there. I assume that it is a varible
passed in to a BSFN and therefore is volatile.
However, if you can find the function that tells the
job to PrintImmediate, you may be able to do what you
need.
There is no place to say this UBE always prints Immediately and that UBE does not. As people said before, you either change your ini file so every UBE prints immediately or none of them print immediately. If you have your ini file set to false you have to click on print immediate every time you submit a job. If you go into a UBE in development mode there are some print constants which you can set to always send a UBE to a specific printer or to print a UBE in CSV mode but there is nothing yet that you can check to indicate that a specific UBE always executes as print immediate. Rumor is it is coming in B9, at least it has been requested for B9.
I haven't followed this thread from the beginning so excuse me if this is
repetitive!!
Here's how I control my printing.
1. Set all JDE.ini to PrintImmediate=TRUE and SaveOutput=TRUE
2. Create a bogus printer in OneWorld (ie it doesn't exist on your
network) : OWINTERNAL
3. I usually make this everybody's default printer. Users can still get
their UBE from work with server jobs OR when they submit the UBE they can
change there printer to a network one and it will print immediately.
4. You can also use the default printer program to assign a specific
report and version to either the OWINTERNAL printer (UBE goes to WSJ) or
an existing network printer (UBE will print immediately).
Sean Gilbert
JDEdwards Consultant
PricewaterhouseCoopers
Montreal
Tel: 514.205.5000 x3619
Fax: 450.655.0163
Jim
<jloesel@qwest. To: Sean Gilbert/CA/MCS/PwC@Americas-CA
net> cc:
Sent by: Subject: Re: RE: Print immediate stored?...
owner-jdelist@j
delist.com
11/02/2001
10:17 AM
Please respond
to jdelist
There is no place to say this UBE always prints Immediately and that UBE
does not. If you go into a UBE in development mode there are some print
constants which you can set to always send a UBE to a specific printer or
to print a UBE in CSV mode but there is nothing yet that you can check to
indicate that a specific UBE always executes as print immediate. Rumor is
it is coming in B9
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.