limit on queues
good day everyone,

i have a question regarding queues in service manager. i have come across many articles "including official ms documentation" suggesting to keep the number of queues to a minimum due to the extra load it puts on the workflow server.

so what i'm after is how everyone manages the access to the work items. i have seen cireson videos where there is a queue for finance that includes everything finance and then there is a queue for everyone else.

what i want is to limit what everyone can see as it might not only be finance that has sensitive information.

i am planning to add all our departments into service manager. i work at a university so it includes everything from it, hr, finance, facilities, etc and all the sub-departments for students and staff. 

as you can see this will be a lot of queues and i want to plan this correctly so we don't have issues in the future.

i was thinking of creating a queue for all the top level departments as this will limit access to a degree, but i'm not sure if it is the best way to approach this.

what i have done this far is as follow:
create ad groups for each sub-department and add the analysts to the relevant groups.
in lists create hierarchy of department\subdepartment for ir and sr
create queue based ir and sr, and criteria are "support group = department\subdepartment"
create group, included members is the ad group.
create user role, select required queues, ci's, catalog groups, tasks, views templates and add the  ad group to users.

so far i have only added two departments and 4 sub-departments. but like mentioned earlier i'm planning to add the rest of the university departments soon.

i know this is a mouth full, but i would really appreciate your input on how you have implemented this in your environments as i can't really find any info on how to implement this besides "keep the queues to a minimum"

any input will be highly appreciated
gerhard
this is a terrific question and i am glad you asked it.  as i am only in the beginning stages of planning to implement this here (it has not been a requirement yet, but will be soon), i can only add some preliminary thoughts to yours:

microsoft should bold, underline, highlight, and add 50 exclamation points to that statement about keeping queues to a minimum.  the performance hit is staggering, if your system has a high number of concurrent users.  you probably won't notice it in your dev or test environments if there aren't many simultaneous testers, however.

so in the spirit of getting the most protection from the fewest number of queues, i am asking some of the following questions:
* is it sufficient to classify ticket data along the lines of "sensitive, private, privileged" or some other such division, so that i could only create queues based on the sensitivity level of information, and not have to split it further by department/team/function/etc.?  this is a business question that will vary for everyone, of course.
* if the above is possible, i can add a classification enum to the tickets and develop a procedure for which should be selected, and base the queue on its value.  if it is not, or if my ticket category or support team already tells me what i need to know, then this is not even necessary.
* if data sensitivity is not a viable way to divide queues, then do i have certain support groups that need a queue, and all others would not belong to a queue?

in any scenario i have described or implied, this means that (most) teams can see each others' tickets.  this is not a problem for me in this environment, but might be for others.  as long as i wrap a queue around the most sensitive tickets, i do not mind if the rest are out in the open.

again, i have not proven these thoughts in production yet, but hopefully it helps to some degree.
1) form controls use a list box for the names of the conference rooms;use datetimepicker for scheduling the reservation...set the format property to custom;set the customformat property to mm dd yyyy hh mm ssof course, will also need ok button2) dataset up the data file like this:room date time1st floor, 6/8/21, 14:00:002nd floor, 6/9/21, 10:00:003rd floor, 6/8/21, 13:30:00reads these records from the file to determine if there is a conflict.if the room is available at the requested time, writes the reservation tothe file (in append mode) and displays a message box saying the reservationis complete. otherwise display a message box saying the room is unavailableat that time. the cme group has education courses that cover most everything about the products they carry. i don’t want to make a mistake and give you bad information. here is a link to their site and there is a video on this page that goes over margins.

[image]

[margin: know what's needed - cme group](https://www.cmegroup.com/education/courses/introduction-to-futures/margin-know-what-is-needed.html)

t… imho the best solution is to put the proxy`s to an bi

[image]

[business intelligence (bi) - reduce complexity with bi](https://docs.checkmk.com/latest/en/bi.html)

complex relationships can be easily visualized with business intelligence (bi). learn step by step how to build bis – rule-based and dynamically.

… as i had the time, thought i would tidy things up, just one custom query needed, no view required. just change the office names and copy/paste into a custom query 
have a great christmas party! 
select sum(office1) as office1,sum(office2) as office2,sum(office3) as office3,hours from 
((select 
cou… network monitor is the ideal tool for monitoring servers - it does everything real time and i think you likely need to just adjust your thresholds so you get less emails.
spiceworks inventory is not intended to be used for monitoring - you can do some aspects with it, but if you're looking for real time monitoring, you're probably best off finding another tool.  if you want to do asset management and keep an eye on the devices for things like disk space, then we're going to be a good fit.  for 500 workstations, if you can avoid using the agent and just directly scan them, you will be better off from a performance standpoint - assuming the environment is fairly consistent, once you figure out how to scan one workstation, those changes should likely apply to the rest (maybe via gpo).  
i hope this helps somewhat.
jackie. so i have received a response from tasha, and there is a limit, but not on the number of projects you can create/remix. it’s a limit of the time interval.

this week, we put a restriction on the number of projects/collections/teams a new user can create within the first 48 hours of account creation… hello team
could anyone could please help me in knowing the details regarding the job vacancies for mba finance freshers. as i m currently pursuing my mba and want to know about the future in this field so that i can have a clear idea of about my future when i come out to the society. so guys please help me and make me aware of the things so that i can be able to do all things Magda, have you found what you need, yet?


I did this many years ago. It is simple… the 2nd time you do it!  

Exit points are simply “interrupts” that IBM supplies. You can attach programs to them, and the programs will automatically run at that point. For setting your AS/400 up to accept FTP logons, for example, the exit point is:  

QIBM\_QTMF\_SVR\_LOGON and the format you wil use is: TCPL0100.


A program inserted there can control WHO can log on, and when.  

To control WHAT they can do, you use another exit point, QIBM\_QTMF\_SERVER\_REQ and use format VLRQ0100.


My notes (from 1999) say I used the IBM TCP manual to get this info, specifically: TCP/IP manual SC41-5420-01 page I-14.


I do not know if it will allow me to post code here, it is long and complex due to the number of variables and some of them being in hex.


Write me (drow@waxie.com) if you would like me to email you my program code.


David Row  

WAXIE Sanitary Supply  

San Diego, CA





This is a link for [Add-ons for Firefox](https://addons.mozilla.org/en-US/firefox/). These are programs written by users or developers that the browser knows how and when to call. The developers of Firefox designed it to allow external programs to be hooked in by users of the browser.


IBM did something similar for a lot of the TCP/IP and other server functions. (And a lot of other things.) When you connect to the FTP server for example, the server checks to see if a program has been registered to process FTP logon requests. The registered program is an ‘exit program’.


Browser add-ons get an entry added to a file someplace within the browser directory structure. In your iSeries, the entry would be added to the Registration Facility. (Not always, but that’s the commonly recognized object for exit points and programs.) Use WRKREGINF to review your registration facility.


To create an exit program, you need to know the parameter list that will be passed to your program and the exit protocol. To find the parameter list, you should start looking at the documentation for the server the exit program will be associated with. The protocol, the meanings of the parms and what to with them, is also there.


A FTP exit program would be structured after documentation within the [File Transfer Protocol exit programs](http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/rzaiq/rzaiqreferenceexit.htm) topic of the Information Center for your release.


Once registered, a server logon exit program (for example) would be called just before the server decides whether or not to accept the logon. Your exit program directly influences that decision by returning an ‘accept or reject’ parameter. It chooses based on examination of the input parms.


The exit program may control who can and cannot logon, where they may logon from, what times of day logons are accepted, or it might accept all logons — its purpose can be simply to write all logons to a log file or to send a message when particular logons happen. Your exit program can do whatever it is programmed to do at that point in the logon process.


It doesn’t have to be a ‘security’ function. It’s whatever you want it to be.


For the FTP server, there are two general exit points. One is just before a logon is accepted. The other is just before each transaction in a session is processed. You can control individual transactions just as you can logons. (FTP client has its own exit points.)


Most other exit programs work on similar principles.


A few issues complicate things.


* An exit program needs enough authority to do whatever it needs to do; it can’t always rely on the authority of the session user.
* An exit program shouldn’t unduly delay transactions; there’s no way to know how often an exit program may be called, so you don’t want it slowing down every single transaction.
* Exit programs may be called by many instances of a server at the same time; it shouldn’t be locking things that are needed by a different instance.
* IBM changes the interfaces at times and the servers themselves can get PTFs; regular, on-going maintenance can be needed — keep the programs direct with little complication.
* There are other issues, but those are enough to consider.


Code a very simple exit program that accepts the parms and returns an ‘Accept’ indication. Don’t have it do anything except maybe send a message to a message queue. That lets you see how the registration facility works and how the parms work. It also gives you a program that you can register and deregister in the future to check whether or not the server is stilling calling your program correctly. (Problems can happen.)


Tom filter at the backend server only? *any examples are for illustrative purposes only.*  
  
explore alternatives to face-to-face triage and visits. the following options can reduce unnecessary healthcare visits and prevent transmission of respiratory viruses in your facility:
* instruct patients to use available advice lines, patient portals, on-line self-assessment tools, or call and speak to an office/clinic staff if they become ill with symptoms such as fever, cough, or shortness of breath.
* identify staff to conduct telephonic and telehealth interactions with patients. develop protocols so that staff can triage and assess patients quickly.
* determine algorithms to identify which patients can be managed by telephone and advised to stay home, and which patients will need to be sent for emergency care or come to your facility.
* instruct patients that if they have respiratory symptoms they should call before they leave home, so staff can be prepared to care for them when they arrive.
* using your telephone system to deliver messages to incoming callers about when to seek medical care at your facility, when to seek emergency care, and where to go for information about caring for a person with covid at home
* work with department of public health to notify community providers and the public of the above strategies so those individuals who can be managed in the community do not seek care at a healthcare facility thus limiting exposure and conserving resources.


  
**advice and leading practices from customers**  
providence health system has set up an online coronavirus assessment tool that advises low risk patients to care for themselves at home or automatically links them to a nurse hotline. while only available for full use by providence customers, it may be a helpful example.  
[providence: helpful information about the novel coronavirus, covid-19](https://www.providence.org/patients-and-visitors/coronavirus-advisory)  
  
many organizations have established drive-through facilities to test patients. this has the advantage of decreasing the use of personal protective equipment.  
[the new york times:  coronavirus testing goes mobile in seattle.](https://www.nytimes.com/2020/03/13/us/coronavirus-testing-drive-through-seattle.html)  
[stanford medicine:  drive-through coronavirus testing available by appointment at stanford health care](http://med.stanford.edu/news/all-news/2020/03/stanford-offers-drive-through-coronavirus-test.html)  
  
the cdc recommends that a patient’s car can be a useful way to isolate patients who come to an emergency department if an airborne infection isolation room is not immediately available. while waiting for further evaluation, a system can be provided that allows them to wait in a personal vehicle or outside the facility (if medically appropriate) and be notified by phone or other remote methods when it is their turn to be evaluated.  
[cdc: interim guidance for healthcare facilities: preparing for community transmission of covid-19 in the united states](https://www.cdc.gov/coronavirus/2019-ncov/healthcare-facilities/guidance-hcf.html)  
  
**references:**  
[cdc: interim guidance for healthcare facilities: preparing for community transmission of covid-19 in the united states](https://www.cdc.gov/coronavirus/2019-ncov/healthcare-facilities/guidance-hcf.html)  
  
hollander, je, carr bg; virtually perfect? telemedicine for covid-19 nejm march 11, 2020, doi: 10.1056/nejmp2003539  
  
note:  links to website(s) included in this faq may be helpful in the development of emergency plans, however, organizations should ensure they are accessing the most recent publication prior to implementing.