B91300C - Launch Batch Application - With Logging ON

Hi guys,

I am calling UBEs via a custom UBE using BSFN B91300C

The UBEs fire fine. I had this promoted to the DV servers and tried to run it using thin client.
Again, UBEs fire off fine.

The reason I am using B91300C is I wish to run the called UBEs with logging on.

When I try to view the logs in WSJ, E1 cannot find any logs at all.

Any ideas what the issue maybe?

Or does anyone know of any other way to submit a UBE and force logging on?

Thanks

John

Hi John,
Did you observe the Enterprise Server's batch folder?
I mean inside this folder:
\\YourEntServer\DriveLetter$\JDEdwards\E812\DDP\PrintQueue

Cheers Adrian.

I'll ask CNC for the details

[ QUOTE ]


Or does anyone know of any other way to submit a UBE and force logging on?



[/ QUOTE ]

Sure. You can turn on debug logging from BV when you submit your UBE. Same place you override the location, there are check boxes to generate jde.log and jdedebug.log.

Hi Jeremy,

Thanks mate but my point was the users are forgetting to do this
So I was going to do it for them by adding 'wrapper UBE versions' to the menu options

I call the UBE for them with logging on using said BSFN

[ QUOTE ]
Hi guys,

I am calling UBEs via a custom UBE using BSFN B91300C

The UBEs fire fine. I had this promoted to the DV servers and tried to run it using thin client.
Again, UBEs fire off fine.

The reason I am using B91300C is I wish to run the called UBEs with logging on.

When I try to view the logs in WSJ, E1 cannot find any logs at all.

Any ideas what the issue maybe?

Or does anyone know of any other way to submit a UBE and force logging on?

Thanks

John

[/ QUOTE ]

A child UBE that is synchronously launched would have its logs in the parent UBE's process logs (they are the same process/procid). Try that.