Disable Print Immediate

[Xavier Echeverria]

Hi, Everybody,

Please, Is there a way to disable the print immediate even IF the check print immediate in P986162 is checked???

Thanks,
Xavier.

 

[peterbruce]

Xavier,

Without modification to the system, print immediate is set up in the jde.ini. When submitting a UBE to run, print immediate can be set on or off via the check box you mention in P986162.

Further than this, it is not clear (to me at least) what you require. Is the probelm that you are unable to check/uncheck the print immediate checkbox in P986162? Or do you wish, under certain conditions, to override whatever the user does or the jde.ini setting?

 

[renga]

Hi All,

Even I am been searching for the functionality to mass disable print immediate in versions of a JDE report. I need to mention here that print immediate has not been enabled here in the ES jde.ini. but still almost all versions being used have print immediate enabled on the submit jobs screen.I need to know if this check mark can be traced to a flag in a table (Versions List or RDASPEC) so that we may sql it...

Thanks in advance,
Renga

 

[peterbruce]

Renga,

I have had a look at the properties for UBEs, UBE Versions, Job Queues and Printers (in our system) and could not see/find any parameter for printing immediately. The only place this is set in an unmodified system (to my knowledge) is in the JDE.INI file on either the Enterprise Server, Application Server or Fat Client. Our system (E8.11 sp1 Tools 8.96C1) configuration is below (in my signature).

Neither Xavier nor yourself mentioned your system configuration. If your system configuration is different to ours, then there may be another option for setting print immediate. For Xe and prior the same applies as for our system - the only place this is set in an unmodified system (to my knowledge) is in the JDE.INI file on either the Enterprise Server, Application Server or Fat Client.

On the other hand, a number of JDEList members have modified their systems print immediate functionality. Depending on the actual mofications made, there may or may not be another option for setting print immediate.

 

[Zoltan_Gyimesi]

Hi All,

I have not analized the issue in depth, but ifjde.ini setting is the key, then maybe Read INI and Set INI Business Functions are the tools for the solution, using them in the Do Initialize Printer event at Report scope and if you want to "reset" original value, then do it in one of the "last" event of the report.

Regards,

Zoltán

 

[Asma Anwar Hussain]

Hi Zoltan,

When I tried using your suggestion and test locally I couldn't see any difference, I am running the E1 as admin. I am thinking whether the admin rights get reflected or not for the system to update JDE.INI file. Please let me know your thoughts. Thanks.

 

[Kim Schmidt]

Hi Asma, I'll try to answer for Zoltan as we haven't seen him post on the List for several years now. When modifying your jde.ini file, you will need to recycle services in order for the changes to take effect. In other words, when JDE services start up on either a server or your local client, it essentially caches the ini settings at that point. Any changes to the jde.ini file will be ignored until JDE restarts. Hope that helps.

 

[Asma Anwar Hussain]

Thankyou Kim for the reply. In my case, several UBEs are ran from scheduler using CL program and the business problem requires to generate UBE logs for erroring UBEs ONLY without restarting JDE, so this solution doesn't help. I found Tools function X983052.c "VersionListLaunchUBE" and tried using it's logic in a new BSFN to generate UBE logs by setting pUBEVar parameters ("LaunchUBEEx API)to set logs =1 and debugging level = 6. But still, I am not seeing UBE logs generated. Any thoughts or inputs highly appreciated please.

 

[peterbruce]

Hi Asma,

I gave a couple of presentations at the Australian and New Zealand JDE conferences in 2011 and 2012 on a similar topic to your requirement. The titles and abstracts are below. If you want a copy of the MS Powerpoint slide stacks send me a private message containing your email.

2011
Title: Include Work Centre Error Messages in Logs When Importing Transactions Via "Z" Tables
Abstract: It can be frustrating when a transaction import fails and you need to go to the work centre and open all the nodes to get the base errors. The work centre error messages can be put into a log created during the importation processing. The log can then be emailed to the user or perhaps used to create a Help Desk Call. This is enabled by having a master UBE run the entire import process, including the loading of the "Z" tables then processing the data into the normal JDE tables. There are a couple of custom NER business functions that are used in the process that may be used for other purposes as well.

2012
Title: Sending logged live Error Messages from the JDE Work Centre to users when importing into Z –Tables in JDE
Abstract: The work centre error messages from importing "Z" Table Transactions can be put into a log created during the importation processing. The log can then be emailed to the user or perhaps used to create a Help Desk Call. This presentation takes you through the tasks involved in building this functionality.

I have made a couple of posts too:

Work Center Report
DB View over Work Center Messages

If you come across any "broken" links, let me know and I'll see if I can provide you with an "unbroken" link.

If the above could be an option for you, I'm happy to answer any questions you may have. The technical details are in the slide stacks. I can explain/expand on what they contain - even though I've been retired for a couple of years. The presentations are targetted at "Z" table import UBEs, but the process will work with any errors recorded in the Work Centre tables.