Re: Fast v.s. List Threads
Seems silly to me to believe the competition isn't gaining access to the documentation. On Thu, May 1, 2014 at 7:50 AM, Bennett, Craig cbenn...@hydro.mb.ca wrote: ** Locked down – easier to deal with. Had one vendor who password protected the download of a password protected .zip archive of the pdf documentation which was then further locked down to prevent copy print. Now that is useless *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Jason Miller *Sent:* Wednesday, April 30, 2014 1:30 PM *To:* arslist@ARSLIST.ORG *Subject:* Re: Fast v.s. List Threads ** Thought I would share this on the List. I put my ranty pants on for this one (no really, notice the tags): Why do I have to log into bmc.docs.com almost every time I open it? https://communities.bmc.com/message/424094 The recentish docs.bmc.com changes and need to enter credentials multiple times a day the has probably been experinece by many of you. Apparently this is by design. The response I received on a recent ticket for it: no secured system in the work arena will allow 1 day of session validity and at this time no changes will be made. (Login expiration is correctly configured. No secured system in the work will allow 1 day of session validity.) Multiple login is a known issue as we have different apps using different SSO solution. We are already working on that. You cannot have SSO/session active across multiple computers. This is basics of secured system.. I too am looking for an answer as to why is this documentation needs to be so secure? SNOW doesn't secure their doc. Jason On Tue, Apr 29, 2014 at 10:20 PM, Axton axton.gr...@gmail.com wrote: ** Just to help (maybe) solve a long standing problem, let me point this out. I ran a Google search for a quote from the excerpt you cited from the product documentation: The fast queue handles the operations that generally run to completion quickly Guess what result did not show up on the first page of results... BMC's product documentation... What logic they have to withhold their documentation from robots indexing it is beyond me. If memory serves me correctly BMC has gone to lengths to ensure that APIs, documentation, javadoc, systematic workflow documentation, etc. are not available on the web. Maybe someone can help me understand the logic here because it eludes me... On Tue, Apr 29, 2014 at 7:06 PM, William Rentfrow wrentf...@stratacominc.com wrote: ** This is straight out of the ARS configuration guide: *Fast queue* The fast queue handles the operations that generally run to completion quickly without blocking access to the database. The fast queue handles all server operations, except for: Administrative operations that restructure the database. These operations use the administration queue. The ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics, and other API calls (which use the list queue). For more information about API calls, see the *C API Reference*. One or more threads can serve the fast queue if a fast queue is configured. To configure a fast queue, see “Defining queues and configuring threads” on page 160*.* *List queue* The list queue handles AR System operations that might require significant time, block access to the database, or both. Examples of these operations include ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics. One or more threads can serve the list queue if a list queue is configured. To configure a list queue, see “Defining queues and configuring threads” on page 160. *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Andrew Fremont *Sent:* Tuesday, April 29, 2014 1:40 PM *To:* arslist@ARSLIST.ORG *Subject:* Fast v.s. List Threads ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ -- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 Internal Virus Database is out of date. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Fast v.s. List Threads
If that is the logic behind the policy, well, it is illogical. Any smart competitor is going to buy the product and understand it inside and out. That's the nature of business today, particularly with technology. All it serves to do is hurt the people that use the product. I am sure their competition is laughing to themselves at the approach and hopes they keep it up. On Fri, May 2, 2014 at 1:39 PM, Jason Miller jason.mil...@gmail.com wrote: ** Seems silly to me to believe the competition isn't gaining access to the documentation. On Thu, May 1, 2014 at 7:50 AM, Bennett, Craig cbenn...@hydro.mb.cawrote: ** Locked down – easier to deal with. Had one vendor who password protected the download of a password protected .zip archive of the pdf documentation which was then further locked down to prevent copy print. Now that is useless *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Jason Miller *Sent:* Wednesday, April 30, 2014 1:30 PM *To:* arslist@ARSLIST.ORG *Subject:* Re: Fast v.s. List Threads ** Thought I would share this on the List. I put my ranty pants on for this one (no really, notice the tags): Why do I have to log into bmc.docs.com almost every time I open it?https://communities.bmc.com/message/424094 The recentish docs.bmc.com changes and need to enter credentials multiple times a day the has probably been experinece by many of you. Apparently this is by design. The response I received on a recent ticket for it: no secured system in the work arena will allow 1 day of session validity and at this time no changes will be made. (Login expiration is correctly configured. No secured system in the work will allow 1 day of session validity.) Multiple login is a known issue as we have different apps using different SSO solution. We are already working on that. You cannot have SSO/session active across multiple computers. This is basics of secured system.. I too am looking for an answer as to why is this documentation needs to be so secure? SNOW doesn't secure their doc. Jason On Tue, Apr 29, 2014 at 10:20 PM, Axton axton.gr...@gmail.com wrote: ** Just to help (maybe) solve a long standing problem, let me point this out. I ran a Google search for a quote from the excerpt you cited from the product documentation: The fast queue handles the operations that generally run to completion quickly Guess what result did not show up on the first page of results... BMC's product documentation... What logic they have to withhold their documentation from robots indexing it is beyond me. If memory serves me correctly BMC has gone to lengths to ensure that APIs, documentation, javadoc, systematic workflow documentation, etc. are not available on the web. Maybe someone can help me understand the logic here because it eludes me... On Tue, Apr 29, 2014 at 7:06 PM, William Rentfrow wrentf...@stratacominc.com wrote: ** This is straight out of the ARS configuration guide: *Fast queue* The fast queue handles the operations that generally run to completion quickly without blocking access to the database. The fast queue handles all server operations, except for: Administrative operations that restructure the database. These operations use the administration queue. The ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics, and other API calls (which use the list queue). For more information about API calls, see the *C API Reference*. One or more threads can serve the fast queue if a fast queue is configured. To configure a fast queue, see “Defining queues and configuring threads” on page 160*.* *List queue* The list queue handles AR System operations that might require significant time, block access to the database, or both. Examples of these operations include ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics. One or more threads can serve the list queue if a list queue is configured. To configure a list queue, see “Defining queues and configuring threads” on page 160. *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Andrew Fremont *Sent:* Tuesday, April 29, 2014 1:40 PM *To:* arslist@ARSLIST.ORG *Subject:* Fast v.s. List Threads ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ -- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 Internal Virus Database is out of date. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been
Re: Fast v.s. List Threads
You do not need to buy the competitors product. What happens is — people switch from “one product” to “another product” … when they come to you — they tell you what they don’t like about their old product - and what they liked about the old product. It is quite simple really. After awhile — you sort of care less what the competition does - and you do your own thing. The last thing I would want to do is read the docs of a competitor. (I would rather watch a good hockey game — or catch up on sleep) -John On Sat, May 3, 2014 at 11:38 PM, Axton axton.gr...@gmail.com wrote: ** If that is the logic behind the policy, well, it is illogical. Any smart competitor is going to buy the product and understand it inside and out. That's the nature of business today, particularly with technology. All it serves to do is hurt the people that use the product. I am sure their competition is laughing to themselves at the approach and hopes they keep it up. On Fri, May 2, 2014 at 1:39 PM, Jason Miller jason.mil...@gmail.comwrote: ** Seems silly to me to believe the competition isn't gaining access to the documentation. On Thu, May 1, 2014 at 7:50 AM, Bennett, Craig cbenn...@hydro.mb.cawrote: ** Locked down – easier to deal with. Had one vendor who password protected the download of a password protected .zip archive of the pdf documentation which was then further locked down to prevent copy print. Now that is useless *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Jason Miller *Sent:* Wednesday, April 30, 2014 1:30 PM *To:* arslist@ARSLIST.ORG *Subject:* Re: Fast v.s. List Threads ** Thought I would share this on the List. I put my ranty pants on for this one (no really, notice the tags): Why do I have to log into bmc.docs.com almost every time I open it?https://communities.bmc.com/message/424094 The recentish docs.bmc.com changes and need to enter credentials multiple times a day the has probably been experinece by many of you. Apparently this is by design. The response I received on a recent ticket for it: no secured system in the work arena will allow 1 day of session validity and at this time no changes will be made. (Login expiration is correctly configured. No secured system in the work will allow 1 day of session validity.) Multiple login is a known issue as we have different apps using different SSO solution. We are already working on that. You cannot have SSO/session active across multiple computers. This is basics of secured system.. I too am looking for an answer as to why is this documentation needs to be so secure? SNOW doesn't secure their doc. Jason On Tue, Apr 29, 2014 at 10:20 PM, Axton axton.gr...@gmail.com wrote: ** Just to help (maybe) solve a long standing problem, let me point this out. I ran a Google search for a quote from the excerpt you cited from the product documentation: The fast queue handles the operations that generally run to completion quickly Guess what result did not show up on the first page of results... BMC's product documentation... What logic they have to withhold their documentation from robots indexing it is beyond me. If memory serves me correctly BMC has gone to lengths to ensure that APIs, documentation, javadoc, systematic workflow documentation, etc. are not available on the web. Maybe someone can help me understand the logic here because it eludes me... On Tue, Apr 29, 2014 at 7:06 PM, William Rentfrow wrentf...@stratacominc.com wrote: ** This is straight out of the ARS configuration guide: *Fast queue* The fast queue handles the operations that generally run to completion quickly without blocking access to the database. The fast queue handles all server operations, except for: Administrative operations that restructure the database. These operations use the administration queue. The ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics, and other API calls (which use the list queue). For more information about API calls, see the *C API Reference*. One or more threads can serve the fast queue if a fast queue is configured. To configure a fast queue, see “Defining queues and configuring threads” on page 160*.* *List queue* The list queue handles AR System operations that might require significant time, block access to the database, or both. Examples of these operations include ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics. One or more threads can serve the list queue if a list queue is configured. To configure a list queue, see “Defining queues and configuring threads” on page 160. *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Andrew Fremont *Sent:* Tuesday, April 29, 2014 1:40 PM *To:* arslist@ARSLIST.ORG
Re: Fast v.s. List Threads
Locked down – easier to deal with. Had one vendor who password protected the download of a password protected .zip archive of the pdf documentation which was then further locked down to prevent copy print. Now that is useless From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jason Miller Sent: Wednesday, April 30, 2014 1:30 PM To: arslist@ARSLIST.ORG Subject: Re: Fast v.s. List Threads ** Thought I would share this on the List. I put my ranty pants on for this one (no really, notice the tags): Why do I have to log into bmc.docs.com almost every time I open it?https://communities.bmc.com/message/424094 The recentish docs.bmc.comhttp://docs.bmc.com changes and need to enter credentials multiple times a day the has probably been experinece by many of you. Apparently this is by design. The response I received on a recent ticket for it: no secured system in the work arena will allow 1 day of session validity and at this time no changes will be made. (Login expiration is correctly configured. No secured system in the work will allow 1 day of session validity.) Multiple login is a known issue as we have different apps using different SSO solution. We are already working on that. You cannot have SSO/session active across multiple computers. This is basics of secured system.. I too am looking for an answer as to why is this documentation needs to be so secure? SNOW doesn't secure their doc. Jason On Tue, Apr 29, 2014 at 10:20 PM, Axton axton.gr...@gmail.commailto:axton.gr...@gmail.com wrote: ** Just to help (maybe) solve a long standing problem, let me point this out. I ran a Google search for a quote from the excerpt you cited from the product documentation: The fast queue handles the operations that generally run to completion quickly Guess what result did not show up on the first page of results... BMC's product documentation... What logic they have to withhold their documentation from robots indexing it is beyond me. If memory serves me correctly BMC has gone to lengths to ensure that APIs, documentation, javadoc, systematic workflow documentation, etc. are not available on the web. Maybe someone can help me understand the logic here because it eludes me... On Tue, Apr 29, 2014 at 7:06 PM, William Rentfrow wrentf...@stratacominc.commailto:wrentf...@stratacominc.com wrote: ** This is straight out of the ARS configuration guide: Fast queue The fast queue handles the operations that generally run to completion quickly without blocking access to the database. The fast queue handles all server operations, except for: Administrative operations that restructure the database. These operations use the administration queue. The ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics, and other API calls (which use the list queue). For more information about API calls, see the C API Reference. One or more threads can serve the fast queue if a fast queue is configured. To configure a fast queue, see “Defining queues and configuring threads” on page 160. List queue The list queue handles AR System operations that might require significant time, block access to the database, or both. Examples of these operations include ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics. One or more threads can serve the list queue if a list queue is configured. To configure a list queue, see “Defining queues and configuring threads” on page 160. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Andrew Fremont Sent: Tuesday, April 29, 2014 1:40 PM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Fast v.s. List Threads ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ No virus found in this message. Checked by AVG - www.avg.comhttp://www.avg.com Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 Internal Virus Database is out of date. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Fast v.s. List Threads
Hi, And to be a little bit less technical, a Submit or a Modify of HPD:HelpDesk might not really be Fast calls, but they are still handled by the Fast threads as they concern a single record only. This rule of *List* calls going to List threads is not 100%. But checking the logs will give you the details of that. But you are probably not interested in it on that level of detail anyway... Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011) Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13): * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. To be slightly more technical than William, the fast threads handle all single API process requests, like a submit, and the list threads handle multiple API requests. Rick On Apr 29, 2014 2:35 PM, Andrew Fremont andrewfrem...@gmail.com wrote: ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Fast v.s. List Threads
Thought I would share this on the List. I put my ranty pants on for this one (no really, notice the tags): Why do I have to log into bmc.docs.com almost every time I open it? https://communities.bmc.com/message/424094 The recentish docs.bmc.com changes and need to enter credentials multiple times a day the has probably been experinece by many of you. Apparently this is by design. The response I received on a recent ticket for it: no secured system in the work arena will allow 1 day of session validity and at this time no changes will be made. (Login expiration is correctly configured. No secured system in the work will allow 1 day of session validity.) Multiple login is a known issue as we have different apps using different SSO solution. We are already working on that. You cannot have SSO/session active across multiple computers. This is basics of secured system.. I too am looking for an answer as to why is this documentation needs to be so secure? SNOW doesn't secure their doc. Jason On Tue, Apr 29, 2014 at 10:20 PM, Axton axton.gr...@gmail.com wrote: ** Just to help (maybe) solve a long standing problem, let me point this out. I ran a Google search for a quote from the excerpt you cited from the product documentation: The fast queue handles the operations that generally run to completion quickly Guess what result did not show up on the first page of results... BMC's product documentation... What logic they have to withhold their documentation from robots indexing it is beyond me. If memory serves me correctly BMC has gone to lengths to ensure that APIs, documentation, javadoc, systematic workflow documentation, etc. are not available on the web. Maybe someone can help me understand the logic here because it eludes me... On Tue, Apr 29, 2014 at 7:06 PM, William Rentfrow wrentf...@stratacominc.com wrote: ** This is straight out of the ARS configuration guide: *Fast queue* The fast queue handles the operations that generally run to completion quickly without blocking access to the database. The fast queue handles all server operations, except for: Administrative operations that restructure the database. These operations use the administration queue. The ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics, and other API calls (which use the list queue). For more information about API calls, see the *C API Reference*. One or more threads can serve the fast queue if a fast queue is configured. To configure a fast queue, see “Defining queues and configuring threads” on page 160*.* *List queue* The list queue handles AR System operations that might require significant time, block access to the database, or both. Examples of these operations include ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics. One or more threads can serve the list queue if a list queue is configured. To configure a list queue, see “Defining queues and configuring threads” on page 160. *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Andrew Fremont *Sent:* Tuesday, April 29, 2014 1:40 PM *To:* arslist@ARSLIST.ORG *Subject:* Fast v.s. List Threads ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ -- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 Internal Virus Database is out of date. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Fast v.s. List Threads
Thanks for the information. Andrew. On Wed, Apr 30, 2014 at 7:33 AM, Campbell, Paul (Paul) p...@avaya.com wrote: ** Here is a link to a BMC Communities article that is the best I’ve ever seen about fast and list threads, good work from David Still https://communities.bmc.com/community/bmcdn/bmc_atrium_and_foundation_technologies/bmc_remedy_ar_system/blog/2013/09/13/the-pulse-addressing-server-side-performance-problems--queues-threads *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Axton *Sent:* Wednesday, April 30, 2014 1:20 AM *To:* arslist@ARSLIST.ORG *Subject:* Re: Fast v.s. List Threads ** Just to help (maybe) solve a long standing problem, let me point this out. I ran a Google search for a quote from the excerpt you cited from the product documentation: The fast queue handles the operations that generally run to completion quickly Guess what result did not show up on the first page of results... BMC's product documentation... What logic they have to withhold their documentation from robots indexing it is beyond me. If memory serves me correctly BMC has gone to lengths to ensure that APIs, documentation, javadoc, systematic workflow documentation, etc. are not available on the web. Maybe someone can help me understand the logic here because it eludes me... On Tue, Apr 29, 2014 at 7:06 PM, William Rentfrow wrentf...@stratacominc.com wrote: ** This is straight out of the ARS configuration guide: *Fast queue* The fast queue handles the operations that generally run to completion quickly without blocking access to the database. The fast queue handles all server operations, except for: Administrative operations that restructure the database. These operations use the administration queue. The ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics, and other API calls (which use the list queue). For more information about API calls, see the *C API Reference*. One or more threads can serve the fast queue if a fast queue is configured. To configure a fast queue, see “Defining queues and configuring threads” on page 160*.* *List queue* The list queue handles AR System operations that might require significant time, block access to the database, or both. Examples of these operations include ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics. One or more threads can serve the list queue if a list queue is configured. To configure a list queue, see “Defining queues and configuring threads” on page 160. *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Andrew Fremont *Sent:* Tuesday, April 29, 2014 1:40 PM *To:* arslist@ARSLIST.ORG *Subject:* Fast v.s. List Threads ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ -- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 Internal Virus Database is out of date. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Fast v.s. List Threads
Neither does Microsoft, Oracle, etc. Why put something onerous in the way of customers? Should be making it much easier to use to get help, rather than harder….. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jason Miller Sent: Wednesday, April 30, 2014 2:30 PM To: arslist@ARSLIST.ORG Subject: Re: Fast v.s. List Threads ** Thought I would share this on the List. I put my ranty pants on for this one (no really, notice the tags): Why do I have to log into bmc.docs.com almost every time I open it?https://communities.bmc.com/message/424094 The recentish docs.bmc.comhttp://docs.bmc.com changes and need to enter credentials multiple times a day the has probably been experinece by many of you. Apparently this is by design. The response I received on a recent ticket for it: no secured system in the work arena will allow 1 day of session validity and at this time no changes will be made. (Login expiration is correctly configured. No secured system in the work will allow 1 day of session validity.) Multiple login is a known issue as we have different apps using different SSO solution. We are already working on that. You cannot have SSO/session active across multiple computers. This is basics of secured system.. I too am looking for an answer as to why is this documentation needs to be so secure? SNOW doesn't secure their doc. Jason On Tue, Apr 29, 2014 at 10:20 PM, Axton axton.gr...@gmail.commailto:axton.gr...@gmail.com wrote: ** Just to help (maybe) solve a long standing problem, let me point this out. I ran a Google search for a quote from the excerpt you cited from the product documentation: The fast queue handles the operations that generally run to completion quickly Guess what result did not show up on the first page of results... BMC's product documentation... What logic they have to withhold their documentation from robots indexing it is beyond me. If memory serves me correctly BMC has gone to lengths to ensure that APIs, documentation, javadoc, systematic workflow documentation, etc. are not available on the web. Maybe someone can help me understand the logic here because it eludes me... On Tue, Apr 29, 2014 at 7:06 PM, William Rentfrow wrentf...@stratacominc.commailto:wrentf...@stratacominc.com wrote: ** This is straight out of the ARS configuration guide: Fast queue The fast queue handles the operations that generally run to completion quickly without blocking access to the database. The fast queue handles all server operations, except for: Administrative operations that restructure the database. These operations use the administration queue. The ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics, and other API calls (which use the list queue). For more information about API calls, see the C API Reference. One or more threads can serve the fast queue if a fast queue is configured. To configure a fast queue, see “Defining queues and configuring threads” on page 160. List queue The list queue handles AR System operations that might require significant time, block access to the database, or both. Examples of these operations include ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics. One or more threads can serve the list queue if a list queue is configured. To configure a list queue, see “Defining queues and configuring threads” on page 160. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Andrew Fremont Sent: Tuesday, April 29, 2014 1:40 PM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Fast v.s. List Threads ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ No virus found in this message. Checked by AVG - www.avg.comhttp://www.avg.com Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 Internal Virus Database is out of date. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ Portions of this message may be confidential under an exemption to Ohio's public records law or under a legal privilege. If you have received this message in error or due to an unauthorized transmission or interception, please delete all copies from your system without disclosing, copying, or transmitting this message. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Fast v.s. List Threads
Why, it's for your safety, and to serve you better. You don't hate security and America and puppies, do you? Rick On Apr 30, 2014 11:56 AM, Jason Miller jason.mil...@gmail.com wrote: ** Thought I would share this on the List. I put my ranty pants on for this one (no really, notice the tags): Why do I have to log into bmc.docs.com almost every time I open it? https://communities.bmc.com/message/424094 The recentish docs.bmc.com changes and need to enter credentials multiple times a day the has probably been experinece by many of you. Apparently this is by design. The response I received on a recent ticket for it: no secured system in the work arena will allow 1 day of session validity and at this time no changes will be made. (Login expiration is correctly configured. No secured system in the work will allow 1 day of session validity.) Multiple login is a known issue as we have different apps using different SSO solution. We are already working on that. You cannot have SSO/session active across multiple computers. This is basics of secured system.. I too am looking for an answer as to why is this documentation needs to be so secure? SNOW doesn't secure their doc. Jason On Tue, Apr 29, 2014 at 10:20 PM, Axton axton.gr...@gmail.com wrote: ** Just to help (maybe) solve a long standing problem, let me point this out. I ran a Google search for a quote from the excerpt you cited from the product documentation: The fast queue handles the operations that generally run to completion quickly Guess what result did not show up on the first page of results... BMC's product documentation... What logic they have to withhold their documentation from robots indexing it is beyond me. If memory serves me correctly BMC has gone to lengths to ensure that APIs, documentation, javadoc, systematic workflow documentation, etc. are not available on the web. Maybe someone can help me understand the logic here because it eludes me... On Tue, Apr 29, 2014 at 7:06 PM, William Rentfrow wrentf...@stratacominc.com wrote: ** This is straight out of the ARS configuration guide: *Fast queue* The fast queue handles the operations that generally run to completion quickly without blocking access to the database. The fast queue handles all server operations, except for: Administrative operations that restructure the database. These operations use the administration queue. The ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics, and other API calls (which use the list queue). For more information about API calls, see the *C API Reference*. One or more threads can serve the fast queue if a fast queue is configured. To configure a fast queue, see “Defining queues and configuring threads” on page 160*.* *List queue* The list queue handles AR System operations that might require significant time, block access to the database, or both. Examples of these operations include ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics. One or more threads can serve the list queue if a list queue is configured. To configure a list queue, see “Defining queues and configuring threads” on page 160. *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Andrew Fremont *Sent:* Tuesday, April 29, 2014 1:40 PM *To:* arslist@ARSLIST.ORG *Subject:* Fast v.s. List Threads ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ -- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 Internal Virus Database is out of date. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Fast v.s. List Threads
Just to help (maybe) solve a long standing problem, let me point this out. I ran a Google search for a quote from the excerpt you cited from the product documentation: The fast queue handles the operations that generally run to completion quickly Guess what result did not show up on the first page of results... BMC's product documentation... What logic they have to withhold their documentation from robots indexing it is beyond me. If memory serves me correctly BMC has gone to lengths to ensure that APIs, documentation, javadoc, systematic workflow documentation, etc. are not available on the web. Maybe someone can help me understand the logic here because it eludes me... On Tue, Apr 29, 2014 at 7:06 PM, William Rentfrow wrentf...@stratacominc.com wrote: ** This is straight out of the ARS configuration guide: *Fast queue* The fast queue handles the operations that generally run to completion quickly without blocking access to the database. The fast queue handles all server operations, except for: Administrative operations that restructure the database. These operations use the administration queue. The ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics, and other API calls (which use the list queue). For more information about API calls, see the *C API Reference*. One or more threads can serve the fast queue if a fast queue is configured. To configure a fast queue, see “Defining queues and configuring threads” on page 160*.* *List queue* The list queue handles AR System operations that might require significant time, block access to the database, or both. Examples of these operations include ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics. One or more threads can serve the list queue if a list queue is configured. To configure a list queue, see “Defining queues and configuring threads” on page 160. *From:* Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] *On Behalf Of *Andrew Fremont *Sent:* Tuesday, April 29, 2014 1:40 PM *To:* arslist@ARSLIST.ORG *Subject:* Fast v.s. List Threads ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ -- No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 Internal Virus Database is out of date. _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Fast v.s. List Threads
To be slightly more technical than William, the fast threads handle all single API process requests, like a submit, and the list threads handle multiple API requests. Rick On Apr 29, 2014 2:35 PM, Andrew Fremont andrewfrem...@gmail.com wrote: ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Fast v.s. List Threads
Here is a link to a BMC Communities article that is the best I’ve ever seen about fast and list threads, good work from David Still https://communities.bmc.com/community/bmcdn/bmc_atrium_and_foundation_technologies/bmc_remedy_ar_system/blog/2013/09/13/the-pulse-addressing-server-side-performance-problems--queues-threads From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Axton Sent: Wednesday, April 30, 2014 1:20 AM To: arslist@ARSLIST.ORG Subject: Re: Fast v.s. List Threads ** Just to help (maybe) solve a long standing problem, let me point this out. I ran a Google search for a quote from the excerpt you cited from the product documentation: The fast queue handles the operations that generally run to completion quickly Guess what result did not show up on the first page of results... BMC's product documentation... What logic they have to withhold their documentation from robots indexing it is beyond me. If memory serves me correctly BMC has gone to lengths to ensure that APIs, documentation, javadoc, systematic workflow documentation, etc. are not available on the web. Maybe someone can help me understand the logic here because it eludes me... On Tue, Apr 29, 2014 at 7:06 PM, William Rentfrow wrentf...@stratacominc.commailto:wrentf...@stratacominc.com wrote: ** This is straight out of the ARS configuration guide: Fast queue The fast queue handles the operations that generally run to completion quickly without blocking access to the database. The fast queue handles all server operations, except for: Administrative operations that restructure the database. These operations use the administration queue. The ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics, and other API calls (which use the list queue). For more information about API calls, see the C API Reference. One or more threads can serve the fast queue if a fast queue is configured. To configure a fast queue, see “Defining queues and configuring threads” on page 160. List queue The list queue handles AR System operations that might require significant time, block access to the database, or both. Examples of these operations include ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics. One or more threads can serve the list queue if a list queue is configured. To configure a list queue, see “Defining queues and configuring threads” on page 160. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG] On Behalf Of Andrew Fremont Sent: Tuesday, April 29, 2014 1:40 PM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Fast v.s. List Threads ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ No virus found in this message. Checked by AVG - www.avg.comhttp://www.avg.com Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 Internal Virus Database is out of date. _ARSlist: Where the Answers Are and have been for 20 years_ _ARSlist: Where the Answers Are and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Fast v.s. List Threads
Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
Re: Fast v.s. List Threads
This is straight out of the ARS configuration guide: Fast queue The fast queue handles the operations that generally run to completion quickly without blocking access to the database. The fast queue handles all server operations, except for: Administrative operations that restructure the database. These operations use the administration queue. The ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics, and other API calls (which use the list queue). For more information about API calls, see the C API Reference. One or more threads can serve the fast queue if a fast queue is configured. To configure a fast queue, see “Defining queues and configuring threads” on page 160. List queue The list queue handles AR System operations that might require significant time, block access to the database, or both. Examples of these operations include ARExport, ARGetListEntry, ARGetListEntryWithFields, and ARGetEntryStatistics. One or more threads can serve the list queue if a list queue is configured. To configure a list queue, see “Defining queues and configuring threads” on page 160. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Andrew Fremont Sent: Tuesday, April 29, 2014 1:40 PM To: arslist@ARSLIST.ORG Subject: Fast v.s. List Threads ** Hi, What are the main differences between the two? I can't any docs about these threads. Which one handle the requests from users via Mid-tier, or WUT clients. Thanks _ARSlist: Where the Answers Are and have been for 20 years_ No virus found in this message. Checked by AVG - www.avg.comhttp://www.avg.com Version: 2014.0.4355 / Virus Database: 3882/7371 - Release Date: 04/20/14 Internal Virus Database is out of date. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Where the Answers Are, and have been for 20 years
