|
Well, it's funny that you mention IASPs, because I have been playing with them for a week or two, and I have been sending input back into the lab so fast that they are drowning in it. One problem is that if you have existing ASP management software, the implementation as it came out in V5R2 may break that software. Making an IASP available a seismic database event, and making one unavailable is also and cancels a number of system jobs, which if done by QSYSOPR with the QSYSOPR message queue in breakmode will interrupt your task 7 making the job a bitch (the message is sev 50). The overhead for making it available/unavailable is inverse proportional to the ratio of the number of objects in *SYSBASE (asps 1-32) and the number of objects in the IASP. Al Barsa, Jr. Barsa Consulting Group, LLC i comes before p, x, and z... e-gads 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com rob@xxxxxxxxx Sent by: midrange-l-bounce To s@xxxxxxxxxxxx Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> 05/01/2003 09:22 cc AM Subject Independent ASP Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxx nge.com> NOT as a high availability solution, but as a possible solution to reduce downtime it has been suggested to us that we investigate using an independent ASP. That way when we bring down MACHINE1 we can switch that stuff over to MACHINE2. This way downtime due to ptf's, upgrades, etc, should be kept at a minimum. My concerns would be: - User profiles. - All the PC's. I suppose at that time we could switch the DNS to route them to the new machine (another reason why host tables are the root of all evil). - BPCS keys. I suppose we could explain this to SSA and they'd give us keys. However we might probably keep the static libraries holding each key out of the IASP. Any other considerations? Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.