RE: Documenting code changes -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: RE: Documenting code changes
From: Cyndi Bradberry <CyndiB@xxxxxxxx>
Date: Fri, 27 Sep 2013 20:45:24 +0000
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

In the interests of full disclosure, we have purchased MKS Implementer, we have split our Series I into 3 systems, Production, Dev & QA. But, as of today, MKS has not been successfully installed. I hope that it will take over a majority of this work for us, because I don't feel real productive keying in numbers to the serialization area. I asked if on a new program did I have to enter the ticket number on each line....they're thinking about it. :-(

Cyndi B.
Boise, ID

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2026 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.