[U2] Strange Selection Behavior
Hi All - I am getting strange results with selections that I am hoping someone else has encountered and can help me resolve. We have SB+ running on UV. I don't have the same issues running on Unidata. I have a BASIC program I have written that constructs a select statement based on the criteria specified in a screen by the user, then executes the constructed selection statement. Something like (although the real one is more complex): SEL.CMD = 'SELECT CUSTOMER WITH CUST.NUM = ' : CUST.NUM : ' AND WITH CUST.TYPE = ' : CUST.TYPE : '' EXECUTE SEL.CMD CAPTURING OUTPUT Indexes are built on the dictionaries and are working properly. When we test the constructed select statement at TCL, the results are retuned under 2 seconds. When it executes inside the BASIC program, it takes approximately 24 seconds to return the same results. We tried adding a NO.INDEX to the statement, which adds 6 seconds to the select at TCL but just a couple of seconds within the BASIC program. Nothing else we have tried has had any effect. Has anyone encountered this type of behavior? Thanks, Steve Long Spyderweb Technical Services, Inc. (360) 687-8797 Washington (503) 406-8797 Oregon (866) 354-5913 Fax ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Strange Selection Behavior
What do the queried fields look like? Are they actual fields or calculated fields? SB+ defined? -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Steve Long Sent: Tuesday, June 14, 2011 4:38 PM To: U2-Users@listserver.u2ug.org Subject: [U2] Strange Selection Behavior Hi All - I am getting strange results with selections that I am hoping someone else has encountered and can help me resolve. We have SB+ running on UV. I don't have the same issues running on Unidata. I have a BASIC program I have written that constructs a select statement based on the criteria specified in a screen by the user, then executes the constructed selection statement. Something like (although the real one is more complex): SEL.CMD = 'SELECT CUSTOMER WITH CUST.NUM = ' : CUST.NUM : ' AND WITH CUST.TYPE = ' : CUST.TYPE : '' EXECUTE SEL.CMD CAPTURING OUTPUT Indexes are built on the dictionaries and are working properly. When we test the constructed select statement at TCL, the results are retuned under 2 seconds. When it executes inside the BASIC program, it takes approximately 24 seconds to return the same results. We tried adding a NO.INDEX to the statement, which adds 6 seconds to the select at TCL but just a couple of seconds within the BASIC program. Nothing else we have tried has had any effect. Has anyone encountered this type of behavior? Thanks, Steve Long Spyderweb Technical Services, Inc. (360) 687-8797 Washington (503) 406-8797 Oregon (866) 354-5913 Fax ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users html body Dave Davis Team Lead, Ramp;D P: 614-875-4910 x108 F: 614-875-4088 E: dda...@harriscomputer.com [http://www.harriscomputer.com/images/signatures/HarrisSchools.gif] [http://www.harriscomputer.com/images/signatures/DivisionofHarris.gif] 6110 Enterprise Parkway Grove City, OH 43123 www.harris-schoolsolutions.com This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. /body /html ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Strange Selection Behavior
Well they are a bit different because they are shared between two systems and we need to construct them the same on both. They are all I-descriptors. Thanks, Steve Long Spyderweb Technical Services, Inc. (360) 687-8797 Washington (503) 406-8797 Oregon (866) 354-5913 Fax -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dave Davis Sent: Tuesday, June 14, 2011 1:44 PM To: U2 Users List Subject: Re: [U2] Strange Selection Behavior What do the queried fields look like? Are they actual fields or calculated fields? SB+ defined? -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Steve Long Sent: Tuesday, June 14, 2011 4:38 PM To: U2-Users@listserver.u2ug.org Subject: [U2] Strange Selection Behavior Hi All - I am getting strange results with selections that I am hoping someone else has encountered and can help me resolve. We have SB+ running on UV. I don't have the same issues running on Unidata. I have a BASIC program I have written that constructs a select statement based on the criteria specified in a screen by the user, then executes the constructed selection statement. Something like (although the real one is more complex): SEL.CMD = 'SELECT CUSTOMER WITH CUST.NUM = ' : CUST.NUM : ' AND WITH CUST.TYPE = ' : CUST.TYPE : '' EXECUTE SEL.CMD CAPTURING OUTPUT Indexes are built on the dictionaries and are working properly. When we test the constructed select statement at TCL, the results are retuned under 2 seconds. When it executes inside the BASIC program, it takes approximately 24 seconds to return the same results. We tried adding a NO.INDEX to the statement, which adds 6 seconds to the select at TCL but just a couple of seconds within the BASIC program. Nothing else we have tried has had any effect. Has anyone encountered this type of behavior? Thanks, Steve Long Spyderweb Technical Services, Inc. (360) 687-8797 Washington (503) 406-8797 Oregon (866) 354-5913 Fax ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users html body Dave Davis Team Lead, Ramp;D P: 614-875-4910 x108 F: 614-875-4088 E: dda...@harriscomputer.com [http://www.harriscomputer.com/images/signatures/HarrisSchools.gif] [http://www.harriscomputer.com/images/signatures/DivisionofHarris.gif] 6110 Enterprise Parkway Grove City, OH 43123 www.harris-schoolsolutions.com This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message. /body /html ___ 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] Strange Selection Behavior
Hi Steve, Have you tried running the command as a LIST with an INFORM on the end? It should show you how the system is treating the way the selection works. You may need to data through an 'Enter' statement in the execute. LIST CUSTOMER WITH CUST.NUM = 999 AND WITH CUST.TYPE = XXX INFORM Stuart. -Original Message- Hi All - I am getting strange results with selections that I am hoping someone else has encountered and can help me resolve. We have SB+ running on UV. I don't have the same issues running on Unidata. I have a BASIC program I have written that constructs a select statement based on the criteria specified in a screen by the user, then executes the constructed selection statement. Something like (although the real one is more complex): SEL.CMD = 'SELECT CUSTOMER WITH CUST.NUM = ' : CUST.NUM : ' AND WITH CUST.TYPE = ' : CUST.TYPE : '' EXECUTE SEL.CMD CAPTURING OUTPUT Indexes are built on the dictionaries and are working properly. When we test the constructed select statement at TCL, the results are retuned under 2 seconds. When it executes inside the BASIC program, it takes approximately 24 seconds to return the same results. We tried adding a NO.INDEX to the statement, which adds 6 seconds to the select at TCL but just a couple of seconds within the BASIC program. Nothing else we have tried has had any effect. Has anyone encountered this type of behavior? Thanks, Steve Long ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Strange Selection Behavior
Hi Steve This may be an issue of the EXECUTE creating another shell to perform the select which the tcl prompt does not require. There has been past discussions of the use of EXECUTE and PERFORM for this reason. However I am not sure that there is an difference for Universe and the PERFORM command is there for functionality. Someone may be able to clarify that. Mind you it should not cause a 22 second issue. Do a print of the cmnd before the execute and capture it in a como. You might see something strange in the way that the command is being constructed. David Jordan ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Strange Selection Behavior
Hi Steve, It could be the CAPTURING clause causing you grief. Check the number of files in the UVTEMP directory. If there are a large number it could be that the OS is taking a long time to create the capturXXX file to store the results for the CAPTURING clause of the EXECUTE command. You could test this by removing the CAPTURING clause from the EXECUTE to see if it performs any better. If it does improve, and you are using the CAPTURING clause to hide the output of the select then look into the HUSH ON|OFF command. Regards, Gregor -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Steve Long Sent: Wednesday, 15 June 2011 6:38 AM To: U2-Users@listserver.u2ug.org Subject: [U2] Strange Selection Behavior Hi All - I am getting strange results with selections that I am hoping someone else has encountered and can help me resolve. We have SB+ running on UV. I don't have the same issues running on Unidata. I have a BASIC program I have written that constructs a select statement based on the criteria specified in a screen by the user, then executes the constructed selection statement. Something like (although the real one is more complex): SEL.CMD = 'SELECT CUSTOMER WITH CUST.NUM = ' : CUST.NUM : ' AND WITH CUST.TYPE = ' : CUST.TYPE : '' EXECUTE SEL.CMD CAPTURING OUTPUT Indexes are built on the dictionaries and are working properly. When we test the constructed select statement at TCL, the results are retuned under 2 seconds. When it executes inside the BASIC program, it takes approximately 24 seconds to return the same results. We tried adding a NO.INDEX to the statement, which adds 6 seconds to the select at TCL but just a couple of seconds within the BASIC program. Nothing else we have tried has had any effect. Has anyone encountered this type of behavior? Thanks, Steve Long Spyderweb Technical Services, Inc. (360) 687-8797 Washington (503) 406-8797 Oregon (866) 354-5913 Fax ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Message protected by DealerGuard: e-mail anti-virus, anti-spam and content filtering. http://www.pentanasolutions.com Click here to report this message as spam: https://login.mailguard.com.au/report/1CvNKu7Zp8/1yOzkbOV9fOILTpT5SHfdr/2.4 This email and any attachments to it are confidential. You must not use, disclose or act on the email if you are not the intended recipient. Liability limited by a scheme approved under Professional Standards Legislation. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Strange Selection Behavior
If you have indexes built on these fields try using selectindex. Jerry On 6/14/2011 3:38 PM, Steve Long wrote: Hi All - I am getting strange results with selections that I am hoping someone else has encountered and can help me resolve. We have SB+ running on UV. I don't have the same issues running on Unidata. I have a BASIC program I have written that constructs a select statement based on the criteria specified in a screen by the user, then executes the constructed selection statement. Something like (although the real one is more complex): SEL.CMD = 'SELECT CUSTOMER WITH CUST.NUM = ' : CUST.NUM : ' AND WITH CUST.TYPE = ' : CUST.TYPE : '' EXECUTE SEL.CMD CAPTURING OUTPUT Indexes are built on the dictionaries and are working properly. When we test the constructed select statement at TCL, the results are retuned under 2 seconds. When it executes inside the BASIC program, it takes approximately 24 seconds to return the same results. We tried adding a NO.INDEX to the statement, which adds 6 seconds to the select at TCL but just a couple of seconds within the BASIC program. Nothing else we have tried has had any effect. Has anyone encountered this type of behavior? Thanks, Steve Long Spyderweb Technical Services, Inc. (360) 687-8797 Washington (503) 406-8797 Oregon (866) 354-5913 Fax ___ 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
