Hi Brian,
/snip I received an email between my last response and this one that said (a lot of things, but basically) that many sites (the grater percentage) don't know what they pay for their software because a) it's done by another department or their boss, or b) they only think about it when they first license the product and don't think about the cost involved until they either run low on budget and are trying to save some amount or they have a problem that makes them unhappy with the product that they are currently paying for. Is that true across the board with you people? /esnip All invoices have to be routed to our Accounts Payable folks to get paid here. In good budget times, and at the very last minute usually <g>, the Accounts Payable folks would ask the technical contact (the sysprog) if the software was still being used and if there were any changes planned. Then the invoice would get paid. Vendors generally would NOT send an info copy of the invoice to the sysprog or a reminder of renewal time. :-( Now that we are in our 4th year of very bad budget (layoffs and LOTS of cuts) a senior sysprog has to justo every single piece of software that is billed, regardless of how much it costs. Tucked in behind the existing process, a justo for each and every product has to be written and approved up the line before the invoice can be paid. This can cause a lot of delay in getting the bill paid. My experience with having to write justos and try to keep keys up to date, is that if the vendor will email a renewal notice with a courtesy copy of the invoice to the senior sysprog (listed technical contact) - and ALSO send the invoice directly to Accounts Payable, payments have a much better chance of happening on time - without the need for temporary keys or extra stress. Linda ----- Original Message ----- From: "Brian Westerman" <[email protected]> To: [email protected] Sent: Thursday, December 29, 2011 6:42:29 PM Subject: Re: cpu / machine identification We have DR support in our software, but I was under the impression that most of the DR sites were running the OS under VM and they simulated the serial anyway. I suppose their are sites that do not run the DR under VM, but don't the sites who don't run under VM know the serial number ahead of time, and wouldn't it be already built into the software, or they have a already setup job to enter the new serial(s)? I know I would have it set up if it were me. This also has nothing to do with the question, but I have always thought that the vendor should be compensated for support of the DR testing anyway. (this will probably cause a lot of angry responses). It's a separate processor and the vendor has to support a problem that might occur on it just like they would if it were the primary processor, which may not have the issue. If that were the case, then the vendor has to support your DR test for free. Now if you are paying $50k for the software, it's probably a reasonable expectation, but if you are paying $2K to $5K it's not as reasonable. I received an email between my last response and this one that said (a lot of things, but basically) that many sites (the grater percentage) don't know what they pay for their software because a) it's done by another department or their boss, or b) they only think about it when they first license the product and don't think about the cost involved until they either run low on budget and are trying to save some amount or they have a problem that makes them unhappy with the product that they are currently paying for. Is that true across the board with you people? Brian On Thu, 29 Dec 2011 17:39:58 -0500, Scott Ford <[email protected]> wrote: >ZMan I am pretty well versed in pc/unix/mf and learning Appleseed... >Btw I wasn't a fan of CPU/serials because DR was such a pita without new >product patches,etc for new CPUs.. > >Sent from my iPad > >On Dec 29, 2011, at 2:40 PM, zMan <[email protected]> wrote: > >> On Thu, Dec 29, 2011 at 10:25 AM, Scott Ford <[email protected]> wrote: >>> As A vendor I understand the CPU/serial situation but one has to consider >>> the less than honest customers and 'yes' I have experience that also >>> >>> Sent from my iPad >> >> ...points to the liabilities of communicating using mobile devices? :-) >> -- >> zMan -- "I've got a mainframe and I'm not afraid to use it" >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
