SPL procid=0?

IDS 12.10 Solaris 10 I mentioned this as a sort of aside in a previous post, but have been unable to determine any answer from further research. Before I open a tech support case, just trying one more time, here. Does anyone know what is meant by a procid=0? I have enabled auditing for the single event of EXSP (execution of a stored procedure). In a few hours, I gathered several hundred thousand events. Almost half of them are for procid=0. I am not aware that any such procid exists. (The reported error code for this SPL is also always 0.) Might anyone know what it means? Thank you for any clues. Regards, DG

Any chance these might be built-in functions (e.g. lower()), or sysdbopen/sysdbclose? From: "DAVID GROVE" <david.grove@alaska.gov> To: ids@iiug.org Date: 10/07/2017 01:04 AM Subject: SPL procid=0? [40023] Sent by: ids-bounces@iiug.org IDS 12.10 Solaris 10 I mentioned this as a sort of aside in a previous post, but have been unable to determine any answer from further research. Before I open a tech support case, just trying one more time, here. Does anyone know what is meant by a procid=0? I have enabled auditing for the single event of EXSP (execution of a stored procedure). In a few hours, I gathered several hundred thousand events. Almost half of them are for procid=0. I am not aware that any such procid exists. (The reported error code for this SPL is also always 0.) Might anyone know what it means? Thank you for any clues. Regards, DG ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Original post: IDS 12.10 Solaris 10 I mentioned this as a sort of aside in a previous post, but have been unable to determine any answer from further research. Before I open a tech support case, just trying one more time, here. Does anyone know what is meant by a procid=0? I have enabled auditing for the single event of EXSP (execution of a stored procedure). In a few hours, I gathered several hundred thousand events. Almost half of them are for procid=0. I am not aware that any such procid exists. (The reported error code for this SPL is also always 0.) Might anyone know what it means? Thank you for any clues. Regards, DG Response: Well, from looking at the code we are passing in the same thing everyplace where we appear to be auditing that event. Based on that, I'm not sure if it would be a situation where that field isn't always getting set properly, or if there are some situations where we hit the auditing code but we don't really have a procid available (so we are just defaulting it to 0). If I get some more time I might try and turn auditing on for 1 of my test systems and see if I can generate any of those procid 0 entries to see if they should or shouldn't be there. Jacques Renaut HCL Informix Support

That sounds like an interesting possibility, because procid=0 sure isn't a UDR. But, I don't think I can determine that. DG

Thank you for your interest and effort. I don't think I can do anything more to figure it out. DG

Well so far in some simple testing, I haven't gotten any procid=0 lines. I've tried sysdbopen/sysdbclose (they don't seem to add anything to the audit output) and I also tried like upper/lower and while they aren't SPL, they seem to generate a line with a negative procid. The procedures I have tried are pretty simple so far. I haven't tried nested procedure yet, or C udr's (of the non-built in variety). Jacques

Thank you, Jacques. Our system, although extensive, is not very complex. For example, no C UDR's. Just a thousand, or so, SPLs. I do appreciate your help. It really seems strange to me. But then, most unexplained behavior is strange until it is explained, and then seems very reasonable and natural. DG

I have opened a tech support case on this. Will advise with results. DG

Hi, just a shot in the dark: could these be run by the dbscheduler ? Regards, Martin -- Martin Fuerderer Informix Development Germany HCL Technologies Germany GmbH Frankfurter Ring 17 80807 Munich, Germany e-mail: martin.fuerderer1@de.ibm.com [1]http://www.hcltech.com/de --DISCLAIMER-- ---------------------------------------------------------------------- ---------------------------------------------------------------------- -------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ---------------------------------------------------------------------- ---------------------------------------------------------------------- -------- From: "DAVID GROVE" <david.grove@alaska.gov> To: ids@iiug.org Date: 10/07/2017 01:04 AM Subject: SPL procid=0? [40023] Sent by: ids-bounces@iiug.org _________________________________________________________________ IDS 12.10 Solaris 10 I mentioned this as a sort of aside in a previous post, but have been unable to determine any answer from further research. Before I open a tech support case, just trying one more time, here. Does anyone know what is meant by a procid=0? I have enabled auditing for the single event of EXSP (execution of a stored procedure). In a few hours, I gathered several hundred thousand events. Almost half of them are for procid=0. I am not aware that any such procid exists. (The reported error code for this SPL is also always 0.) Might anyone know what it means? Thank you for any clues. Regards, DG ********************************************************************** ********* Forum Note: Use "Reply" to post a response in the discussion forum. References 1. http://www.hcltech.com/de

Thank you for the suggestion. We don't know, because we don't know their names or procid's. (The only thing we know is that onaudit is reporting execution of SPL with procid=0, which is necessarily an error since there are zero SPLs with procid=0.) But, from your question, I wonder... Is it the case that stored procedures invoked from the Scheduler are NOT AUDITED BY onaudit??? If so, this could explain another problem we are having. We have a stored procedure that is executed every 30 minutes by the scheduler, but it NEVER shows up in the audit file. I was about to open another tech support case to troubleshoot this problem. But, from your question, I gather it might be a known issue. I didn't see any mention of this problem in the documentation, but then maybe I just missed it. Thank you. DG

Just some FYI... I opened a tech support case for this, but, so far, not much progress. Tech Support doesn't have access to an instance of version 12.10C3, so they cannot set up any testing to attempt to duplicate. They also reviewed Informix source code, and cannot find any explanation for the behavior. Troubleshooting continues. Seems to be a real mystery. I think we will probably upgrade to current Informix, soon, and see if the problem still exists. Tech support indicated that there were issues with the data dictionary in 12.10FC3, and that some fixes were made in subsequent releases, and maybe the problem might not exist in newer version. DG

Just a brief summary of the Tech Support case. Tech Support did not have access to an instance of Solaris IDS 12.10FC3. They did have access to the IDS source code. They examined it, but could not explain the observed behavior. The bottom line is that they suggested we upgrade to a newer IDS point release, and that that might fix the problem because our version, 12.10FC3, was known to have bugs in the data dictionary, which is what the engineer suspected as the problem. We agreed to close the case without resolution. Expect to upgrade Informix in the next few months, and will re-open the case if the problem exists in the current version. It was, and remains, a mystery. DG