D3 equivalent to COMO

#21

On Apr 26, 11:29 am, "chandru murthi" <cmurthi... (AT) xyzseeinggreen (DOT) net>
wrote:

Quote:

I'm not completely clear about this. Do you mean the item is created in
Backgrounds.Output once the job terminates
and that the Backgrounds job is archived to Backgrounds.Report?

chandru

"Jim" <jmr... (AT) comcast (DOT) net> wrote in message

news:1177599060.673235.58570 (AT) r30g2000prh (DOT) googlegroups.com...

On Apr 24, 6:24 pm, art <artma... (AT) triad (DOT) rr.com> wrote:
Jim wrote:
This may not be a solution for you but D3 does have the BACKGROUND
process that logs output to the Backgrounds.Output file for a phantom
process. We have used it for capturing activity, similar to COMO, for
phantom jobs. Works well.

Interesting. I had to pull up the manual for this one. I like the
syntax for feeding inputs. Do you know what happens if you run in
background a program that (by design) executes endlessly? Does the
record in the backgrounds.output get written only when the job
terminates? And if the job has been running for days, and the output
could be REAL big?

Art

The item is created in Backgrounds.Output once the job terminates.
Additionally, the Backgrounds job is archived to Backgrounds.Report.

Jim- Hide quoted text -

- Show quoted text -

Sorry, I wasn't seeing confirmation that my reply was posted. I've
cleaned up the redundancies. ;-)

#22

About 20 years ago I wrote a COMO-like process that would monitor the
I/O buffer (TSBEG? OBBEG?) of other ports in Ultimate systems. D3
does have a PEEK mode, so if we knew exactly where to find the IO
buffers in D3 I could write something like this.

I checked with RD and filed an action item for an enhancement to add a
COMO feature to D3. Until that gets processed, I also asked if they
would tell me how to get from the PCB to those buffers in D3.
Unfortunately but understandably the map of user workspace is
confidential and cannot be released. I'll see if I can figure out a
way to do this but 1) it will probably be different between NT and
*nix, and 2) unless someone is funding this it will always fall to the
bottom of my deep to-do list.

I like Luke's idea for a proxy but it requires a bit too much code in
too many places. If I needed to do this at gun-point, I'd use
Accuterm, tell the client to capture screens, then tell the client to
return the screens back to the DBMS. It's not elegant but it can be
made transparent. Feel free to disagree with the approach but when
you're going from no solution at all to one that's functional but not
asthetically pleasing to the psyche, I think it's reasonable to take
what's available until something else comes along.

As always, I can write it if someone is willing to pay for it.
TG@ removethisNebula-RnD.com

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

D3 equivalent to COMO

comp.databases.pick comp.databases.pick

Re: D3 equivalent to COMO - 04-26-2007 , 02:23 PM

Re: D3 equivalent to COMO - 04-28-2007 , 10:18 PM