> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of Schneiderwent, Craig
>
> > Why are you not using the LE runtime?
>
> Not my code, not my app. As I said in the original note,
> "The program object detecting the error was last compiled in
> 1999 with VS COBOL II [...]." At that time, apparently the
> SYSLIB for the program binder step in the change management
> system was set up to use the VS COBOL II runtime library
> first.
Perhaps just a "nit", but one worth "picking": In LE, the library used
at bind-time (CEE.SCEELKED) is not the runtime library (CEE.SCEERUN). I
don't remember if VS COBOL II had separate bind-time and run-time
libraries; we "modernized" our COBOL portfolio in 1999 using Y2K as our
"excuse", and haven't looked back.
> I also don't set those SYSLIB concatenations. _If_
> using the LE runtime is _known_ to fix this, I have
> ammunition to get such things changed.
It may well turn out that the only way it will be "known to fix" the
problem in your environment is to try it.
> > That alone may fix it.
>
> I agree. So far, no one is interested in fixing it. It
> happens rarely.
> I'd like it fixed before "rarely" becomes "all the time."
> Like maybe when we go to z/OS 1.9 in a couple of months.
If not z/OS 1.9, then certainly your next CICS upgrade will "force" you
off the language-specific runtime libraries.
-jc-
----------------------------------------------------------------------
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
