output_cycle problem

This topic has 2 replies, 2 voices, and was last updated 13 years, 4 months ago by John Perks.

Creator

Topic
May 5, 2011 at 4:53 pm #52456

John Perks
Participant

I have a UPOC protocol thread configured using Advanced Scheduling, with 4 event entries. All the entries use tclprocs with ARGS specified, and examine a common directory that is not in the $HCIROOT/ filesystem for files to process. When the output_cycle command is executed against the process the normal process log in the process directory records the execution of the command, but the new process log is written to that common directory. And until the process is bounced, the new log in the common directory is the current process log. There are no other anomalies with the process and UPOC thread except the unorthodox location of the process log. I need to correct this and obviously update the process log in the process directory at all times.
Creator

Topic

Viewing 1 reply thread

Author

Replies
- May 5, 2011 at 5:40 pm #74273
  
  Jim Kosloskey
  Participant
  
  John,
  
  Just a thought – do any of the Tcl procs change the working directory?
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- May 5, 2011 at 7:04 pm #74274
  
  John Perks
  Participant
  
  That was it.
  
  Since the thread was UPOC protocol, not fileset-local, the PROTOCOL.IBDIR was not available and I had done a cd to a different directory in one of the tcl procs. That changed it immediately for the process’ command thread, and the rest is academic.
  
  Thanks.
Author

Replies

Viewing 1 reply thread

The forum ‘Cloverleaf’ is closed to new topics and replies.