[U2] [UV] Messing with file triggers and error 30107

2014-04-08 Thread Peter Cheney
Hi Everyone,

Just thought I'd post a solution to a recent problem to do with a file trigger 
that was driving me up the wall, across the ceiling and down the other side...

I'd made a mod to a particular file trigger to write to an item to a new file 
and all of a sudden the unirpcd started complaining with this error:

IBMU2.UODOTNET.UniSubroutineException: [IBM U2][UODOTNET - 
UNICLIENT][ErrorCode=30107] The subroutine failed to complete successfully
   at IBMU2.UODOTNET.UniSubroutine.Call()
   at 
FirstMac.Core.BusinessService.FunderService.Connection.Ultracs.UltracsUniDkConnection.Execute(String
 subroutineName, String[] arguments, Boolean logRequest, Boolean logResponse)


Searching around the usual haunts I found a few similar questions but nothing 
that answered my issue. Am still not entirely sure what other conditions this 
error 30107 covers but if you ever get this error then I recommend you check 
the file permissions of any newly created files that your code/modification is 
trying to write to.

Regards,
Peter


Peter Cheney
Ultracs Developer
t 07 3017 8837 | f 07 3002 8400
e peter.che...@firstmac.com.au
w firstmac.com.au


 ---
Note: 
This email (inc all attachments) is for the use of the intended recipient(s) 
only.
Privileged or confidential information may be contained in this communication. 
If you have received this email in error, please notify the sender immediately 
and then delete all copies of this message from your computer network. If you 
are not the intended recipient, you must not keep, use, disclose, copy or 
distribute this email without the author's prior permission. If you are the 
intended recipient and you do not wish to receive similar electronic messages 
from us in future, then please respond to the sender to this effect. 
We have taken precautions to minimise the risk of transmitting software 
viruses, but advise you to carry out your own virus checks on this email and 
its attachments. We do not accept liability for any loss or damage caused by 
software viruses and do not represent that this transmission is free from 
viruses or other defects. 
Firstmac Limited (ABN 59 094 145 963) (AFSL 290600) 
 ---
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


Re: [U2] [UV] Messing with file triggers and error 30107

2014-04-08 Thread Jacques G.
Hello,

If the program being called by the trigger is catalogued globally and that 
program was changed by an installation, you need to drop the trigger and re-add 
it otherwise it will fail when the trigger is called.





 From: Peter Cheney peter.che...@firstmac.com.au
To: U2 Users List u2-users@listserver.u2ug.org 
Sent: Tuesday, April 8, 2014 2:05 AM
Subject: [U2] [UV] Messing with file triggers and error 30107
 

Hi Everyone,

Just thought I'd post a solution to a recent problem to do with a file trigger 
that was driving me up the wall, across the ceiling and down the other side...

I'd made a mod to a particular file trigger to write to an item to a new file 
and all of a sudden the unirpcd started complaining with this error:

IBMU2.UODOTNET.UniSubroutineException: [IBM U2][UODOTNET - 
UNICLIENT][ErrorCode=30107] The subroutine failed to complete successfully
   at IBMU2.UODOTNET.UniSubroutine.Call()
   at 
FirstMac.Core.BusinessService.FunderService.Connection.Ultracs.UltracsUniDkConnection.Execute(String
 subroutineName, String[] arguments, Boolean logRequest, Boolean logResponse)


Searching around the usual haunts I found a few similar questions but nothing 
that answered my issue. Am still not entirely sure what other conditions this 
error 30107 covers but if you ever get this error then I recommend you check 
the file permissions of any newly created files that your code/modification is 
trying to write to.

Regards,
Peter


Peter Cheney
Ultracs Developer
t 07 3017 8837 | f 07 3002 8400
e peter.che...@firstmac.com.au
w firstmac.com.au


---
Note: 
This email (inc all attachments) is for the use of the intended recipient(s) 
only.
Privileged or confidential information may be contained in this communication. 
If you have received this email in error, please notify the sender immediately 
and then delete all copies of this message from your computer network. If you 
are not the intended recipient, you must not keep, use, disclose, copy or 
distribute this email without the author's prior permission. If you are the 
intended recipient and you do not wish to receive similar electronic messages 
from us in future, then please respond to the sender to this effect. 
We have taken precautions to minimise the risk of transmitting software 
viruses, but advise you to carry out your own virus checks on this email and 
its attachments. We do not accept liability for any loss or damage caused by 
software viruses and do not represent that this transmission is free from 
viruses or other defects. 
Firstmac Limited (ABN 59 094 145 963) (AFSL 290600) 
---
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


Re: [U2] [UV] Messing with file triggers and error 30107

2014-04-08 Thread Bill Haskett
This is pretty much why one builds a single update trigger program and a 
single delete trigger program.  Then, from within those subroutines, 
call(s) are made to the actual subroutines that do something.  This way, 
you can actually use local subroutines to do trigger work.


Bill


- Original Message -
*From:* jacque...@yahoo.com
*To:* U2 Users List u2-users@listserver.u2ug.org
*Date:* 4/8/2014 8:45 AM
*Subject:* Re: [U2] [UV] Messing with file triggers and error 30107

Hello,

If the program being called by the trigger is catalogued globally and that 
program was changed by an installation, you need to drop the trigger and re-add 
it otherwise it will fail when the trigger is called.





  From: Peter Cheney peter.che...@firstmac.com.au
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Tuesday, April 8, 2014 2:05 AM
Subject: [U2] [UV] Messing with file triggers and error 30107
  


Hi Everyone,

Just thought I'd post a solution to a recent problem to do with a file trigger 
that was driving me up the wall, across the ceiling and down the other side...

I'd made a mod to a particular file trigger to write to an item to a new file 
and all of a sudden the unirpcd started complaining with this error:

IBMU2.UODOTNET.UniSubroutineException: [IBM U2][UODOTNET - 
UNICLIENT][ErrorCode=30107] The subroutine failed to complete successfully
at IBMU2.UODOTNET.UniSubroutine.Call()
at 
FirstMac.Core.BusinessService.FunderService.Connection.Ultracs.UltracsUniDkConnection.Execute(String
 subroutineName, String[] arguments, Boolean logRequest, Boolean logResponse)


Searching around the usual haunts I found a few similar questions but nothing 
that answered my issue. Am still not entirely sure what other conditions this 
error 30107 covers but if you ever get this error then I recommend you check 
the file permissions of any newly created files that your code/modification is 
trying to write to.

Regards,
Peter


Peter Cheney
Ultracs Developer
t 07 3017 8837 | f 07 3002 8400
e peter.che...@firstmac.com.au
w firstmac.com.au


---
Note:
This email (inc all attachments) is for the use of the intended recipient(s) 
only.
Privileged or confidential information may be contained in this communication. 
If you have received this email in error, please notify the sender immediately 
and then delete all copies of this message from your computer network. If you 
are not the intended recipient, you must not keep, use, disclose, copy or 
distribute this email without the author's prior permission. If you are the 
intended recipient and you do not wish to receive similar electronic messages 
from us in future, then please respond to the sender to this effect.
We have taken precautions to minimise the risk of transmitting software 
viruses, but advise you to carry out your own virus checks on this email and 
its attachments. We do not accept liability for any loss or damage caused by 
software viruses and do not represent that this transmission is free from 
viruses or other defects.
Firstmac Limited (ABN 59 094 145 963) (AFSL 290600)
---
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users


Re: [U2] jobnotify: Error 913 occurred

2014-04-08 Thread regalitare
The strangest source of Broken Pipe I've encountered was with Internet 
Explorer run from servers to web servers!  In my case it was a home-grown 
program that had a web management console. Regular desktop MSIE, chrome, 
firefox, safari, opera, just about everything worked fine, except the IE on 
servers.

Steve...


-Original Message-
From: Daniel McGrath dmcgr...@rocketsoftware.com
To: U2 Users List u2-users@listserver.u2ug.org
Sent: Thu, Mar 20, 2014 11:31 am
Subject: Re: [U2] jobnotify: Error 913 occurred


I've never heard of this issue and our issue tracking system doesn't show any 
customers having reported it.

jobnotify: Error 913 occurred indicates that the parent process has detected 
the child process terminating via catching a SIG. The number after 9, 13 in 
this 
case, indicates which signal.

13 is SIGPIPE, which means a broken pipe.

If you haven't already, please report it to your support provider.

Cheers,
Dan

From: u2-users-boun...@listserver.u2ug.org 
u2-users-boun...@listserver.u2ug.org 
on behalf of Leverett, Brendon brendon.lever...@spotless.com.au
Sent: Wednesday, 19 March 2014 9:39 PM
To: U2 Users List (u2-users@listserver.u2ug.org)
Subject: Re: [U2] jobnotify: Error 913 occurred

Nearly one week and no responses...

Do I assume no one encountered the 'jobnotify: Error 913 occurred' message or 
has any knowledge of it.

Regards,
Brendon Leverett

From: Leverett, Brendon
Sent: Friday, 14 March 2014 11:09 AM
To: U2 Users List (u2-users@listserver.u2ug.org)
Subject: jobnotify: Error 913 occurred

We have recently upgraded Universe (10.2.4 to 11.1.15) and are now finding some 
unusual activity around phantom jobs and the documented change to NOTIFY ON.

There are a lot of details behind the scenes but in summary:
- started  a job via phantom command (phantom SYNC.COPY.BNET)
- noticed 90 mins later that this job had crashed. This crash happens for 
various reasons but is more frequently crashing since the upgrade
- restarted the same job with the same phantom command
At this time the following 3 lines of text was returned to the user's session:
jobnotify: Error 913 occurred
[15466830] SYNC.COPY.BNET - terminated
Phantom process started with process ID 33161456

Seems the 1ST 2 lines of text related to the previous phantom and 3rd line 
related to the phantom just started.

My Q is:
Does anyone have any ideas about the specific message
jobnotify: Error 913 occurred


We are running on AIX.

Regards,
Brendon Leverett

** This 
email message and any files transmitted with it may be confidential and 
privileged neither of which is intended to be waived. If you have received this 
communication in error, please reply to this e-mail to notify the sender of its 
incorrect delivery and then delete it and your reply. It is your responsibility 
to check this email and any attachments for viruses and defects before opening 
or sending them on. Spotless collects information about you to provide and 
market our services. For information about use, disclosure and access, see our 
privacy policy at http://www.spotless.com.au Please consider our environment 
before printing this email. 
**
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users

 
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users