Re: Open /COPY member bug

Violaine,

 I just downloaded the latest fixes, cleared the cache, exited WDSC and
restarted - same problem.

 I don't know if this has any bearing on the problem, but the link you
supplied mentions comments after position 81.  These comments start in
position 51.  I think that the compiler ignores any text after member
name, and WDSC doesn't.

 -mark

Hi Mark,

Do you have RSE 6013 applied?  Please see APAR SE26330 (I believe that's
the APAR I opened when you reported the issue):
http://snipurl.com/1dm0q

thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab


wdsci-l-bounces@xxxxxxxxxxxx wrote on 03/21/2007 11:46:22 AM:

Violaine,

 I while back I reported that I was having trouble opening /COPY members
(via the r-clk -> /COPY Member selection), but that it wasn't
consistent.
 *LIBL was not an issue, since some members from the same source file
would open and others wouldn't.

 The statement is:
/COPY QCPYLESRC,SRCMBR               * Paperwork request - fax / email.

 The message on the bottom is:
CPFI9810E: Library QCPYLESRC, not found.

 That message is different from the one that would be generated if the
source member didn't exist (or wasn't in the *LIBL.)

 A colleague finally found the cause.  The parser doesn't stop parsing
after the /COPY statement.  It continues on to parse the comment.  The
"/" in the comment confuses it.

 -mark