It may be necessary to modify the login PROC/Paragraph of an account where the Kourier software has been installed. The primary reason to make this change is that the application login process does not allow phantom processes (which Kourier uses to run services) to login without interactive prompts. It may also be advisable to allow the "kourier" interactive user to by-pass your application login process so that the "kourier" user can have direct access to TCL to facilitate data analysis activities.
001: PA
002: IF @USER.TYPE = "1" THEN GO LOGIN.EXIT
003: DISPLAY PROCESS IS NOT A PHANTOM
004: LOGIN.EXIT:
001: PA
002: IF @USER.TYPE = "1" THEN GO LOGIN.EXIT
003: IF @LOGNAME = "kourier" THEN GO LOGIN.EXIT
004: DISPLAY PROCESS IS NOT A PHANTOM OR THE
kourier USER
005: LOGIN.EXIT:
001: PA
002: IF @TTY = "phantom" THEN GO LOGIN.EXIT
003: DISPLAY PROCESS IS NOT A PHANTOM
004: LOGIN.EXIT:
001: PA
002: IF @TTY = "phantom" THEN GO LOGIN.EXIT
003: IF @LOGNAME = "kourier" THEN GO LOGIN.EXIT
004: DISPLAY PROCESS IS NOT A PHANTOM OR THE
kourier USER
005: LOGIN.EXIT:
On UniVerse systems, you can create a login paragraph associated to a specific user which will by-pass the default login sequence. The example below creates a login paragraph for the kourier user that only sets up terminal characteristics.
ED VOC kourier
001: PA
002: PTERM CASE NOINVERT
001: PQ
002: HKT.ISAPHANTOM
003: P
004: IF A = phantom XExiting LOGIN for phantom
process.
001: PQ
002: HKT.ISAPHANTOM kourier,joesmith
(multiple user names can be specified separated by commas)
003: P
004: IF A = phantom XExiting LOGIN for
phantom/user process.
Kourier Integrator Setup and Administration Guide