There were "bunches" of problems with the COBOL2 translator option
interacting with the DBCS compiler option. I can't (quickly) find a summary
of what APARs fixed which problems. You might want to check out
PKPK26401
and
PK26933:
If you are a SHARE member, you may want to check out
http://shareew.prod.web.sba.com/client_files/callpapers/attach/SHARE_in_Tamp
a_Bay/S8211TR132424.pdf
and
http://shareew.prod.web.sba.com/client_files/callpapers/attach/SHARE_in_Tamp
a_Bay/S8241TR133034.pdf
""Paul Peplinski"" <[EMAIL PROTECTED]> wrote in message
news:<[EMAIL PROTECTED]>...
> I could separately post this to DB2 and CICS lists but I suspect I will
> get as good (or better) response here.
>
> Does anyone have advice on migrating to CICS and DB2 COBOL coprocessors
> opposed to separate translate and precompile steps? I tried it before for
> CICS (2002?) but encountered problems. I also seem to recall issues in
> testing products but my memory is a little hazy there. Perhaps there some
> other peculiarities as well?
>
> This would be under a source management package which would have to
> dynamically generate compiler parms (CICS cannot be used for non-CICS and
> I suspect SQL could be the same).
>
> If you have done so, are there certain levels that work best? We're
> currently Ent COBOL 3.3, CICS/TS 2.3 and DB2 V8.
----------------------------------------------------------------------
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
