9 replies to this topic

[Vlodik Zmyslony]

I've been able to run a ProIV batch process by using 'at' to run the process in the background so that it will continue processing even though the session where it was started is logged off.
The process appears to run correctly, however my only concern is that the logging file shows that proiv is trying to run a 'ps' command and also produces the message
'No controlling Terminal'
I have tried using 'nohup' but even with various traps it will still diconnect if the session is logged off.
Does anyone have any other sugestions on how to call ProIV so that the Process will be imune to hangup?
and/or should I be concerned about the logging output by using the 'at' command?

[Rob Donovan]

HI,

PROIV overrides the unix command nohup!!!

I have complained to support about this and they said that PROIV must allow a kill signal to kill proiv. I think it's compleatly wrong for a program to override unix commands but we all know how impossible it is to get support to see how the 'real world' uses proiv as opposed to how they do.

However, I have written a 'c' routine ( ok 1 line!) that will disable the kill signal that disconnects proiv when a terminal logs out.

You have to compile the routine into the kernel because PROIV also reanables the kill signal every time the logic 'SYSTEM' command is called (very usefull for us!). So you can not call the program using this.

The routine is simply....

ignorehangup()

{
sigignore(SIGHUP);
}

If you compile this into the kernel and then in LOGIC IN of the first function in you batch process you have the following.

001 DISABLE(&#@INTERRUPT)
002 LINK('IGNOREHANGUP')

NOTE: This presumes you have called the 'c' routine 'IGNOREHANGUP' in the kernel.
The DISABLE command is needed or the background process will try to process CTRL-C's that the starting terminal does, and kill the function.

Also you have to put the 'LINK' command after any SYSTEM or SYSTEM-CRT command in any of the functions that are in the background loop.

We use this in a major part of our system to stop background processes from stopping.

Maybe if there are enough people who want to do this we should all complain and get PROIV to make it work properly..... or we could send a comment to DEC and ask them to change their unix manuals to say that the 'nohup'
command does not work with the 'pro' command!!!

Hope this helps

Rob

[Malcolm Fell]

We use a completly different method. First of all the last function being executed must have exit link of OFF.
Then define a unix userid we use onp.
Then start from crontab
/usr/bin/su - onp '-c /admin/scripts/westpac.run'
Then in westpac.run
PROPATH=/production/trust
ORACLE_SID=PROD
export PROPATH ORACLE_SID
cd /production/trust/data.1
pro WBC AMP
lastly the ProIV userid WBC is
CO/DIV: AMP OPERATOR ID: WBC PASSWORD:
LOGON TO LINK FUNCTION: WBCCTL1U FORCED HELP? Y TRANSPARENT LOGON? Y

[Rob Donovan]

Hi,

Then why isn't there a PROIV command to do this,because obviously people want to do this!!

Also, how do you get a 'new' group ID, any examples?

Rob

[Rob Donovan]

Hi,

We don't want a bourne shell command, we want a command in PROIV LOGIC to do this.

With PL/SQL or COBOL I would use the unix NOHUP command which stops the process receiving hangups.

However, for some reason PROIV overides this unix command

Rob

[Rob Donovan]

The problem with that is that BUS/TASKS are only usable through DEV/STUDIO (Am I correct??).

We don't use this so we would not be able to maintain things.

Also our system works fine with the no hangups that I disable (and has done for 3-4 years now). We don't really want to convert to BUS/TASKS at this point.

BTW, do you know if there are many sites that are using BUS/TASKS yet or is it still quite new??

Thanks,

Rob