|
 FAQ's - APPX Software, Inc. : APPX Utility : APPX Runtime Environment : Other Runtime Questions :
Action Logs don't generate |
We run a job for a post and the action log normally behaves correctly,
but on occasion no log is produced. But in a subsequent job for
another group, the action log contains items (usually Warnings) for
this post, as well Warnings from the first post. |
One possibility - check the Start-of-Process and the End-of-Process event points. If these event points have ERROR, WARNING, MESSAGE, or DISPLAY statements, they can cause a problem if executed. They are not valid statements for those event points.
|
Action logs are created automatically when an APPX update process encounters an error or executes an ERROR, WARNING, or MESSAGE statement. Normally, an action log is closed and queued to print at the end of the process that created it. We are not aware of any specific problems relating to the creating and queuing of action logs. Having said that, there must be something that is preventing APPX from closing and queuing the action log. Perhaps the update process is crashing or otherwise ending prematurely and APPX never has an opportunity to close and queue the action log.
|
| You might consider a workaround that also gives you more control over Logs produced, by converting your post's Updates to Output processes. The ILF normally in UPDATE's "Start of Frame" is put into the OUTPUT's "Select Image" ILF series. Explicitly set --- ALTERNATE IMAGE NUMBER = 0 at start of "Select Image". Then set ALTERNATE IMAGE NUMBER = 1 if you run into any CANCEL, ERROR, WARNING, or MESSAGEs. Paint the primary key to the file on the RECORD level OUTPUT image, and the Sort/Control fields onto any RANGE-START/END frames.
You'll have more control over the format of your Logfile, and you can use DISPOSITION functions to direct them. You could also use ILF to update an ancillary error tracking file, if you want a more permanent record of errors encountered, by whom, and when.
|
| [Append to This Answer] |
| 2004-Apr-01 3:34pm
|
Appx/Client timeout duration