If anybody has frequently used tasks with a third party application please help me out. I've been reading the docs in pro4, as well as trying to get the examples to work, and I have had little luck with either approach. I defined a simple function to update a file, and I added it to a task, except after specifying all the necessary parameters (in this case, only 1 parameter) I tried to click ok on the main task manager, and it looked my pro4 session. Each subsequent try produced the same result. The Bus/API examples don't seem to work... any hints, any direction?
Thanks,
Serge
Click the link below to see the new game I'm developing!
Tasks...
Started by
Guest_Serge_*
, Aug 02 2000 06:17 PM
8 replies to this topic
#4
Cleve Haynes
-
- Members
-
- 172 posts
Expert
- Gender:Male
Posted 07 August 2000 - 01:58 AM
Ensure that in pro4.ini, you have USERNAME_VALIDATE=N,
otherwise task won't work. e.g:
[ENVIRONMENT]
USERNAME_VALIDATE=N
PROPATH=d:pro46BOOTS
PRODATA=d:pro46BOOTS
PRORUNTYPE=DEV
GUI=Y
PROTERM=GUICLR
STARTCLIENT=d:pro46PROGUI.EXE /INI:d:pro46LOOPBACK.INI
FSIDEFAULT=PRO-ISAM
ORACLE_DLLNAME=d:pro46PROORA73.DLL
Secondly, for tasks to work on NT, you must have an
[ENVIRONMENT NAMES] section in pro4.ini. This is similar
to defining users. e.g:
[ENVIRONMENT NAMES]
CLEVE=D:PRO46userscleve.ini
PROIVD=D:PRO46usersdemo.ini
It is this (user) name that is used to call the task.
cleve.ini would contain something like:
[ENVIRONMENT]
PROPATH=D:PRO46CLEVE
PRODATA=D:PRO46CLEVEDATA
PRORUNTYPE=DEV
[DATABASE - SQLDEFAULT]
FILETYPE=ORACLE
CONNECTION=CLEVE/CLEVE@DB
SQL_USERNAME=CLEVE
SQL_PASSWORD=CLEVE@DB
In ProIV itself, you also need a special operator setup for
calling tasks.
This operator should have no logon link to function and
no default function defined.
Use the sample program P4_CPP2.exe to test that the task is
being called correctly.
Make use of the error codes this program gives you.
The task error codes are defined in the p4 help.
This will allow you to find out where problems are.
otherwise task won't work. e.g:
[ENVIRONMENT]
USERNAME_VALIDATE=N
PROPATH=d:pro46BOOTS
PRODATA=d:pro46BOOTS
PRORUNTYPE=DEV
GUI=Y
PROTERM=GUICLR
STARTCLIENT=d:pro46PROGUI.EXE /INI:d:pro46LOOPBACK.INI
FSIDEFAULT=PRO-ISAM
ORACLE_DLLNAME=d:pro46PROORA73.DLL
Secondly, for tasks to work on NT, you must have an
[ENVIRONMENT NAMES] section in pro4.ini. This is similar
to defining users. e.g:
[ENVIRONMENT NAMES]
CLEVE=D:PRO46userscleve.ini
PROIVD=D:PRO46usersdemo.ini
It is this (user) name that is used to call the task.
cleve.ini would contain something like:
[ENVIRONMENT]
PROPATH=D:PRO46CLEVE
PRODATA=D:PRO46CLEVEDATA
PRORUNTYPE=DEV
[DATABASE - SQLDEFAULT]
FILETYPE=ORACLE
CONNECTION=CLEVE/CLEVE@DB
SQL_USERNAME=CLEVE
SQL_PASSWORD=CLEVE@DB
In ProIV itself, you also need a special operator setup for
calling tasks.
This operator should have no logon link to function and
no default function defined.
Use the sample program P4_CPP2.exe to test that the task is
being called correctly.
Make use of the error codes this program gives you.
The task error codes are defined in the p4 help.
This will allow you to find out where problems are.
#5
Guest_Serge_*
Guest_Serge_*
-
- Guests
Posted 07 August 2000 - 03:03 PM
Thanks for the detailed reply Cleve. I amended the .ini file on the server to include what you specified. However, when I run the task example to which p4_cpp2.exe defaults, I still do not get a connection. I tried to create my own task to be sure that it existed, but after I finished defining the parameters through studio (tried to hit the OK button, and dot out) , I again was locked, and I had to shutdown/restart the proiv service. Maybe I'm not placing the proper information in the text fields in the API example, I can't truly be sure. What should I put in the system id/system pwd/ environment text fields?
Thanks again,
Serge
Thanks again,
Serge
#6
Cleve Haynes
-
- Members
-
- 172 posts
Expert
- Gender:Male
Posted 08 August 2000 - 02:02 AM
The system userid & system password fields can be left blank
on an NT system.
The Environment parameter should be set to the environment
name that has been put in the pro4.ini file in the environment
names section.
If you have installed the sample tasks, then this is easy to
test using P4_CPP2.exe:
Computer: your.server.name
Task: TK_Z_TASKTEST
System UserId: (leave blank)
System password: (leave blank)
Operator UserId: TSK
Operator Password: TSK
Co/Div: DEV
(note: this is user above is the special user with no logon
link to function as explained in prior post)
Enviroment: CLEVE (this is in the environment names section of .ini file)
Parameters: TEST1=HELLO,TEST2=CHARLIE
(Note: parameters can be specified in many ways - this is the
easiest.)
The task should return something like:
Output Parameters: (9) Company_Division_Code=DEV,
Operator_ID=TSK,PROIV_Licensee=Your Company,
PROIV_Ver_Date=Dec 15, 99,PROIV_Version=4.6 r2.0.0,
Server_Date=08 AUG 2000,Server_Time=08:54:54,
TEST1=HELLO,TEST2=CHARLIE
Hope this helps!
on an NT system.
The Environment parameter should be set to the environment
name that has been put in the pro4.ini file in the environment
names section.
If you have installed the sample tasks, then this is easy to
test using P4_CPP2.exe:
Computer: your.server.name
Task: TK_Z_TASKTEST
System UserId: (leave blank)
System password: (leave blank)
Operator UserId: TSK
Operator Password: TSK
Co/Div: DEV
(note: this is user above is the special user with no logon
link to function as explained in prior post)
Enviroment: CLEVE (this is in the environment names section of .ini file)
Parameters: TEST1=HELLO,TEST2=CHARLIE
(Note: parameters can be specified in many ways - this is the
easiest.)
The task should return something like:
Output Parameters: (9) Company_Division_Code=DEV,
Operator_ID=TSK,PROIV_Licensee=Your Company,
PROIV_Ver_Date=Dec 15, 99,PROIV_Version=4.6 r2.0.0,
Server_Date=08 AUG 2000,Server_Time=08:54:54,
TEST1=HELLO,TEST2=CHARLIE
Hope this helps!
#7
Guest_Serge_*
Guest_Serge_*
-
- Guests
Posted 08 August 2000 - 03:42 PM
Cleve, thanks again for your detailed response. I have definitely made progress thanks to your advice, but as of now (using the TK_Z_TASKTEST task) I receive the following error: LastErr 46 : Stat: 46 Reason: 99 SubError: 54 I checked the documentation for the error, which is a Kernel Bus Interface error, ( in this case the kernel startup failed ). I can't find what the SubError 54 is, it maybe a system error of some sort. Another minor related question, when I try to create a task, or view an already existing task, and I try to exit the task manager by hitting ok, that task gets locked, and I'm forced to ctrl+alt+del out of it, is this a windows specific problem? Thanks once more for the information 
#8
Cleve Haynes
-
- Members
-
- 172 posts
Expert
- Gender:Male
Posted 09 August 2000 - 01:36 AM
Assuming you have the correct licencing (ie developement
or bus keys installed), then the tasks should work.
If you are using NT workstation and not NT server, then tasks
will NOT work...
Although unlikely, you might be to check for a conflict on
port 5432 (the default port used to listen for task requests)
Hmmmm, I think I am running out of ideas...
I haven't come across any problems with the task maintenance.
or bus keys installed), then the tasks should work.
If you are using NT workstation and not NT server, then tasks
will NOT work...
Although unlikely, you might be to check for a conflict on
port 5432 (the default port used to listen for task requests)
Hmmmm, I think I am running out of ideas...
I haven't come across any problems with the task maintenance.
#9
Glenn Meyers
-
- Members
-
- 221 posts
ProIV Guru
- Gender:Male
- Location:St. Louis, MO, United States
- Interests:I also raise African Gray Parrots and build hot rod automobiles.
Posted 10 August 2000 - 03:59 PM
Make sure that the user TSK does not have a log-on link-to function.
When the task starts up the user it will always try to run this function and you will get a similar error mesage.
Good Luck!
Glenn
When the task starts up the user it will always try to run this function and you will get a similar error mesage.
Good Luck!
Glenn
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Click the link below to see the new game I'm developing!
