In a recent note, "Support, DUNNIT SYSTEMS LTD." said: > Date: Sun, 25 Feb 2007 02:29:15 -0600 > > For a bit of background, our applications are all single CSECT load > modules, with the only common exception being those running under CICS, > that are linked with the CICS execution interface stub (which has so far > shown to be upward/downward compatible for decades). > > It is therefore easiest for us to supply updates in the form of > replacement load modules, meaning we fix the source code, recompile and > relink before packaging. > > What sayeth yee all? > Do you propose to supply them pre-linked with the CICS stub? Are there no licensing problems with this?
You can supply full load modules and install in target libraries with an IEBCOPY step image in the JCLIN. Sounds simple and effecive. However, customers expect PTFs in instream SYSLIN format. The rational objection to delivering load modules is that they proliferate TLIBs. How do you plan to deliver maintenance: o Tapes? o GIMZIP FROMNETWORK format? I know of no other format that supports delivery of load modules. And FROMNETWORK forces customers who are not well network-connected to jump through some awkward hoops. How do you plan to deliver emergency APAR fixes, for which the overnight express deliver latency is troublesome? -- gil -- StorageTek INFORMATION made POWERFUL ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
