We run numerous updates and reports under cron on unix and direct screen output to files by doing the above but adding 2>&1 to the end of the cron line.
Example;
/system/scripts/run_this_script.sh > /system/logs/run_this_script.log 2>&1
It throws out all characters sent to the screen including control characters that move the cursor around the screen etc but you can normally see enough when checking for errors. It's also worth putting UMSG's in certain places in your functions at the start to help.
- ProIV Resource Centre
- → Viewing Profile: Posts: Mark Snowshall
Community Stats
- Group Members
- Active Posts 13
- Profile Views 7,884
- Member Title Member
- Age 57 years old
- Birthday February 5, 1968
-
Gender
Male
-
Location
Nottingham, United Kingdom
Previous Fields
-
First Name
Mark
-
Surname
Snowshall
-
Nationality
English
-
Year Started ProIV
1993
-
Highest ProIV Version Used
7.0
-
Company Working For
Boots
-
Companies Worked For
MDIS,
Pro-IV Systems,
CSC (Munich),
TNT Express World Wide,
TNT Logistics (UK) Ltd.
CEVA Logistics
0
Neutral
User Tools
Latest Visitors
Posts I've Made
In Topic: Error handling when function is run by Unix script
27 November 2009 - 09:49 AM
In Topic: Finding text within functions
18 December 2006 - 03:07 PM
We managed to find a semi-decent search facility in VIP but then manually updated the various places manually in native as when we had imported our system into VIP 47 functions were either rejected or highlighted as having problems.....though they've been working fine for the last 9+ years.
In most places we put a value variable but a couple of places had to be left alone as they were to do with the data rather than visual stuff to be replaced.
Thanks for all the ideas and help but we think we've cracked it all now.
In most places we put a value variable but a couple of places had to be left alone as they were to do with the data rather than visual stuff to be replaced.
Thanks for all the ideas and help but we think we've cracked it all now.
In Topic: Finding text within functions
14 December 2006 - 10:04 AM
Typical, as soon as I raise the question I stumble of the functionality in VIP......worklists!!!!!
Am obvioulsy not upto speed on the intuative menu structure as yet.........
Am obvioulsy not upto speed on the intuative menu structure as yet.........

In Topic: Pro-IV / Unix defunct sessions
25 January 2006 - 03:33 PM
Looks like it was iscollect. Have tried a few tests and we now have both iscollect and iscollect_64 processes running on our development server. This seems to have solved the problem without causing any other problems.
We will keep it like this for the next few days then try it on our live server next week. If no problems, then we will keep both running on the live machine until all the systems have been migrated over.
Thanks for the help guys.
We will keep it like this for the next few days then try it on our live server next week. If no problems, then we will keep both running on the live machine until all the systems have been migrated over.
Thanks for the help guys.
In Topic: Pro-IV / Unix defunct sessions
24 January 2006 - 03:04 PM
Not sure whether they are pro or oracle sessions. We get defunct sessions when we are purely editing functions and not actually running the application. When I do a 'ps -ef' I simply get the following where logged on as user news4 :-
ps -ef |grep pts |grep ta
news4 3925 3375 1 14:11:09 pts/ta 0:00
news4 27970 27969 0 08:15:06 pts/ta 0:00 -ksh
news4 4581 3375 1 14:17:25 pts/ta 0:00
news4 3372 27970 0 14:02:46 pts/ta 0:00 /bin/ksh ./mailnet MAC
news4 3376 3375 2 14:02:46 pts/ta 0:00
news4 3375 3372 0 14:02:46 pts/ta 0:07 /usr/local/pro55/bin/pro MAC MDC
news4 4192 3375 1 14:14:10 pts/ta 0:00
iscollect is set as -rwsr-xr-x
As we still have a version of 4.6 running on the same machine while we migrate our old systems over to 5.5, should we be running iscollect_64 which is what is in the 5.5 directory???
ps -ef |grep pts |grep ta
news4 3925 3375 1 14:11:09 pts/ta 0:00
news4 27970 27969 0 08:15:06 pts/ta 0:00 -ksh
news4 4581 3375 1 14:17:25 pts/ta 0:00
news4 3372 27970 0 14:02:46 pts/ta 0:00 /bin/ksh ./mailnet MAC
news4 3376 3375 2 14:02:46 pts/ta 0:00
news4 3375 3372 0 14:02:46 pts/ta 0:07 /usr/local/pro55/bin/pro MAC MDC
news4 4192 3375 1 14:14:10 pts/ta 0:00
iscollect is set as -rwsr-xr-x
As we still have a version of 4.6 running on the same machine while we migrate our old systems over to 5.5, should we be running iscollect_64 which is what is in the 5.5 directory???
- ProIV Resource Centre
- → Viewing Profile: Posts: Mark Snowshall
- Privacy Policy