[ronald kalmeijer]

Check, I found the proc cl_check_ack. In the Netherlands we use tclprocs from Enovation which are located in de sites.
Thanks for the script.

[ronald kalmeijer]

We don’t have the cl_check_ack tclproc. For that we have a validateReply60 that handle the ACK messages.
Good to know that the Thread must have his own process.
Do you have an example of the shell script? Thanks

[ronald kalmeijer]

Hi Jim,
Thanks for your tcl-script, it it very usefull.
You mentioned also an alert that puts the thread on hold. Can I have the configuration for the alert.

Ronald

[ronald kalmeijer]

ronald kalmeijer wrote:

Thanks Jim I think both solutions are good enough for saving ACK messages. Do you have an example of these solutions (the second one is what I want). At the end we must know if NAK occurred. Besides we can save the message the email is also useful.

[ronald kalmeijer]

Thanks Jim
I think both solutions are good enough for saving ACK messages.
Do you have an example of these solutions.
At the end we must know if NAK occurred. Besides we can save the message an email is also useful.

 

[ronald kalmeijer]

Here is the case.
Sending ADT messages and receiving ACK messages.
Some ADT messages give a NAK message.
Before 19.1 the ACK/NAK messages were saved in a file.
With scripting you can search in the file for a NAK message.
In 19.1 the ACK/NAK messages are only saved in a DB.
Now I want to save the ACK/NAK messages also in a file, so I can search in the file by scripting.
Result is ACK/NAK messages in DB and in file.

[ronald kalmeijer]

The reason for saving the ACK messages into a file is as follow.

Cloverleaf is running on Linux. We want to search in the files with a script. So no actions in Cloverleaf are needed. We have set Retries -1.

 

[ronald kalmeijer]

Hi James,

I turn on the ‘Save Inbound’ allready, so the ACK are saved in the DB.
The ACK messages that I want to saved into a file is for searching through the messages.

Greetings

Ronald

[ronald kalmeijer]

Perhaps I can make it easy. With the stored procedure I would like to send back the date (now) and a default argument (like 1).

[ronald kalmeijer]

I solved the problem.

Instead of ksh I use now bash and the cronjob looks like this:

Code:

55 * * * * bash –login /quovadx/qdx5.6/integrator/maasstad/proces_test

The script proces_test begins with

#! /bin/bash

instead of

#! /usr/bin/ksh

Thanks for the support.

[ronald kalmeijer]

I use the following commandos under the name proces_test:

Code:

#! /usr/bin/ksh
setsite maasstad
hcienginestop -p pacs2
sleep 10
hcienginerun -p pacs2

I can run the script (./proces_test)

If I use the commando crontab -e with the line it doesn’t run:

55 * * * * su hci -c /quovadx/qdx5.6/integrator/maasstad/proces_test

The logging gives me the following output:

Code:

From hci@cl-test01.mcrz.intra  Mon Aug 23 08:55:01 2010
Return-Path:
Received: from cl-test01.mcrz.intra (localhost.localdomain [127.0.0.1])
by cl-test01.mcrz.intra (8.13.8/8.13.8) with ESMTP id o7N6t1dX028977
for ; Mon, 23 Aug 2010 08:55:01 +0200
Received: (from hci@localhost)
by cl-test01.mcrz.intra (8.13.8/8.13.8/Submit) id o7N6t1tg028976;
Mon, 23 Aug 2010 08:55:01 +0200
Date: Mon, 23 Aug 2010 08:55:01 +0200
Message-Id:
From: root@cl-test01.mcrz.intra (Cron Daemon)
To: hci@cl-test01.mcrz.intra
Subject: Cron su hci -c /quovadx/qdx5.6/integrator/maasstad/proces_test
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:

standard in must be a tty

[ronald kalmeijer]

Thxs. I can run the script.

But if I run it with a cron job I got the following message

standard in must be a tty

[Author]

Replies