Hi Rod,

I totally agree with you. The problem you described has technical
challenges that the development team is currently working on.

Regards,
Nazmin Haji




Rod Verity
<rod_verity@coope
rators.ca> To
Sent by: wdsci-l@xxxxxxxxxxxx
wdsci-l-bounces@m cc
idrange.com
Subject
Re: [WDSCI-L] Setting up our own
12/19/2007 10:46 Compile from WDSC
AM


Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>







Nazmin,
Yes I found that EVFEVENT file. There are two problems with this..first
it takes a bit of maneouvering to get to that file. Secondly, when I click
on an error, WDSC actually opens up the "debug" version of the code(the
code that you would see in DEBUG mode). I am not able to change this
version of the code since it is the listing created by the compile.
Just to confirm, is there no way of making the error listing
automatically appear when a CL program is used? Is there a way of making
WDSC open up the EVFEVENT listing? Is there a way of making the error
listing use the actual source listing instead of the listing created from
the compile? Just one note connected to that. The original program is
CSBM9910.SQLCBL. When I finally get the error listing open and click on an
error, it opens up CSBM9910.CBL and positions the code at the error line.
If I want to correct the error, I have to go back to the CSBM9910.SQLCBL
version, find the similiar position and fix the code. This is really not
much better than looking at the joblog listing.
What do other people do when they have multiple different program types
to compile and multiple different libraries where copybooks could reside?
Forcing the programmer to determine if CRTSQLCBL, CRTCICSCBL, CRTCICSMAP or
CRTCBLPGM needs to be run straight out from WDSC leaves a lot of room for
error. Also, it assumes that the person has already changed their library
list to point to where they want to pick up the copybook. WDSC becomes a
tougher sell to our programmers when I tell them they have to do all these
steps, that our current compiler does, manually.
Thanks,
Rod




wdsci-l-request@m
idrange.com
Sent by: To
wdsci-l-bounces@m wdsci-l@xxxxxxxxxxxx
idrange.com cc

Subject
19/12/2007 08:41 WDSCI-L Digest, Vol 5, Issue 810
AM


Please respond to
wdsci-l@midrange.
com







Send WDSCI-L mailing list submissions to
wdsci-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/wdsci-l
or, via email, send a message with subject or body 'help' to
wdsci-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
wdsci-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of WDSCI-L digest..."


*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.


------------------------------

message: 4
date: Wed, 19 Dec 2007 09:43:01 -0500
from: Nazmin Haji <haji@xxxxxxxxxx>
subject: Re: [WDSCI-L] Setting up our own Compile from WDSC

Hi Rod,

If you running your compile commands from CL, the Error List View is not
automatically opened to populate the errors. However, if you specified an
option to generate the events file, say for OPM compiler OPTION(*LSTDBG) or
OPTION(*SRCDBG), an event file containing the errors is generated. You can
manually open this events file in Error List view and proceed normally.
To locate the events file, look in the target library for the compile
command for data file EVFEVENT. If you expand this file, you will see all
the events file, with the same name as the source member and type mbr.
Right click on this choose the option to Show in Error List.
Hope this helps.

Regards,
Nazmin Haji




Rod Verity
<rod_verity@coope
rators.ca> To
Sent by: wdsci-l@xxxxxxxxxxxx
wdsci-l-bounces@m cc
idrange.com
Subject
Re: [WDSCI-L] Setting up our own
12/18/2007 05:56 Compile from WDSC
PM


Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>







Thank you everyone for your replies. Unfortunately, I still can't get the
errors to display in the Iseries Error List. I have added /*
OPTION(*EVENTF) */ to the end of WDSC compile command. I am using the
compile option *LSTDBG. I am hoping the OPM compiler would allow *EVENTF.
When we invoke our compiler we are actually using a CL program that calls
another CL program. The WDSC command looks like following:
ICOMPWD PGM(&N) SRCLIB(&L) SRCFILE(&F) /* OPTION(*EVENTF) */

ICOMPWD calls another CL program which does the CRTSQLCBL command. Is there
anything else I can try or is there anything I can look at to see why WDSC
isn't picking up the error listing?

Thanks,
Rod




wdsci-l-request@m
idrange.com
Sent by: To
wdsci-l-bounces@m wdsci-l@xxxxxxxxxxxx
idrange.com cc

Subject
18/12/2007 12:00 WDSCI-L Digest, Vol 5, Issue 809
PM


Please respond to
wdsci-l@midrange.
com







Send WDSCI-L mailing list submissions to
wdsci-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.midrange.com/mailman/listinfo/wdsci-l
or, via email, send a message with subject or body 'help' to
wdsci-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
wdsci-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of WDSCI-L digest..."


*** NOTE: When replying to this digest message, PLEASE remove all text
unrelated to your reply and change the subject line so it is meaningful.

Today's Topics:

1. Re: Setting up our own Compile from WDSC (Rod Verity)
2. Re: Setting up our own Compile from WDSC (Dave Shaw)
3. Re: Setting up our own Compile from WDSC (Buck)
4. Re: Setting up our own Compile from WDSC (Dave Shaw)


----------------------------------------------------------------------

message: 1
date: Mon, 17 Dec 2007 12:48:26 -0600
from: Rod Verity <rod_verity@xxxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Setting up our own Compile from WDSC


David,
When you say "Make sure the compile command you actually invoke has the
OPTION(*EVENTF) so the necessary information is generated during the
compile." Does that mean the compile command within WDSC or the CRTSQLCBL
command in the CL program being called. I tried it with the WDSC command
and it say "Keyword OPTION not valid for this command." If I put it in the
CRTSQLCBL command it says "*EVENTF not valid for parameter OPTION".
Thanks,
Rod




wdsci-l-request@m
idrange.com
Sent by: To
wdsci-l-bounces@m wdsci-l@xxxxxxxxxxxx
idrange.com cc

Subject
17/12/2007 12:00 WDSCI-L Digest, Vol 5, Issue 808
PM


Please respond to
wdsci-l@midrange.
com







message: 1
date: Mon, 17 Dec 2007 09:55:42 -0600
from: David Gibbs <david@xxxxxxxxxxxx>
subject: Re: [WDSCI-L] Setting up our own Compile from WDSC

Rod Verity wrote:
Regarding setting up our own compile, I read the suggested Wiki and
comments. I added /* *EVENTF SRCMBR(&N) */ to the compile command in
WDSC
and changed the CURLIB to the destination library(where EVFEVENT is) but
I
still don't receive the errors in Iseries error list. Is there such a
thing
as having too many "layers" to the compile command being evoked? We call
a
CL program, which in turn calls a second a CL program which calls a third
CL program to do the appropriate compile. Any comments are welcome.

Make sure the compile command you actually invoke has the
OPTION(*EVENTF) so the necessary information is generated during the
compile.

david

--
System i ... for when you can't afford to be out of business









The information contained in this e-mail message, including any attached
documents, is confidential and may be privileged. It is intended for the
sole use of the recipient(s) to whom it is addressed. If you are not the
intended recipient(s), any review, use, copying, distribution or disclosure
is strictly prohibited. You must take all measures reasonably necessary to
secure and protect any personal information contained in this e-mail and
you must not retain it for longer than necessary. If you have received this
e-mail in error, we ask that you notify us immediately and delete all
copies of this e-mail, and your reply e-mail, and not retain any of its
contents.
______________________________________________________
Les renseignements contenus dans ce courriel, y compris les pi?ces jointes,
sont confidentiels et peuvent ?tre de nature privil?gi?e. Si le pr?sent
courriel ne vous est pas destin?, il vous est strictement interdit de
l'?tudier, de l'utiliser, de le copier, de le distribuer ou d'en d?voiler
le contenu. Vous devez prendre toutes les mesures raisonnables et
n?cessaires afin de s?curiser et de prot?ger tout renseignement personnel
contenu dans ce courriel. Vous devez de plus ?viter de le conserver plus
longtemps que n?cessaire. Si vous avez re?u ce courriel par erreur,
veuillez nous en informer sans d?lai. Veuillez ?galement d?truire tous les
exemplaires du message original et de votre r?ponse, et ne conserver aucune
partie de son contenu.



------------------------------

message: 2
date: Mon, 17 Dec 2007 13:59:58 -0500
from: "Dave Shaw" <daveshaw@xxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Setting up our own Compile from WDSC

Rod,

I'm not David, but...

You're using the OPM SQL Cobol compiler, right? It looks like that one
never had the *EVENTF added to it (someone correct me if I'm wrong). If
that's so, I think you're stuck. Moving to the ILE compiler would probably

be a big deal, wouldn't it?

Dave Shaw
Mohawk Industries

----- Original Message -----
From: "Rod Verity" <rod_verity@xxxxxxxxxxxxxx>
To: <wdsci-l@xxxxxxxxxxxx>
Sent: Monday, December 17, 2007 1:48 PM
Subject: Re: [WDSCI-L] Setting up our own Compile from WDSC



David,
When you say "Make sure the compile command you actually invoke has the
OPTION(*EVENTF) so the necessary information is generated during the
compile." Does that mean the compile command within WDSC or the CRTSQLCBL
command in the CL program being called. I tried it with the WDSC command
and it say "Keyword OPTION not valid for this command." If I put it in the
CRTSQLCBL command it says "*EVENTF not valid for parameter OPTION".
Thanks,
Rod



------------------------------

message: 3
date: Mon, 17 Dec 2007 14:38:03 -0500
from: Buck <kc2hiz@xxxxxxxxx>
subject: Re: [WDSCI-L] Setting up our own Compile from WDSC

Rod Verity wrote:

When you say "Make sure the compile command you actually invoke has
the
OPTION(*EVENTF) so the necessary information is generated during the
compile." Does that mean the compile command within WDSC or the CRTSQLCBL
command in the CL program being called. I tried it with the WDSC command
and it say "Keyword OPTION not valid for this command." If I put it in
the
CRTSQLCBL command it says "*EVENTF not valid for parameter OPTION".

In your WDSC compile command, try adding a comment at the end, like my
OPM SQL RPG compile has:

CRTSQLRPG PGM(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) REPLACE(&R)
OPTION(*LSTDBG) /* OPTION(*EVENTF) */

Right click the member, Compile, Work with compile commands


------------------------------

message: 4
date: Mon, 17 Dec 2007 15:10:04 -0500
from: "Dave Shaw" <daveshaw@xxxxxxxxxxxxx>
subject: Re: [WDSCI-L] Setting up our own Compile from WDSC

Rod,

Buck's post reminded me. OPM SQL RPG creates the event file if you have
option(*lstdbg) specified. Try that with the Cobol compiler and see if it
works.

Dave Shaw
Mohawk Industries

----- Original Message -----
From: "Buck" <kc2hiz@xxxxxxxxx>
Newsgroups: midrange.wdsci-l
To: <wdsci-l@xxxxxxxxxxxx>
Sent: Monday, December 17, 2007 2:38 PM
Subject: Re: [WDSCI-L] Setting up our own Compile from WDSC


Rod Verity wrote:

When you say "Make sure the compile command you actually invoke has
the
OPTION(*EVENTF) so the necessary information is generated during the
compile." Does that mean the compile command within WDSC or the
CRTSQLCBL
command in the CL program being called. I tried it with the WDSC command
and it say "Keyword OPTION not valid for this command." If I put it in
the
CRTSQLCBL command it says "*EVENTF not valid for parameter OPTION".

In your WDSC compile command, try adding a comment at the end, like my
OPM SQL RPG compile has:

CRTSQLRPG PGM(&O/&N) SRCFILE(&L/&F) SRCMBR(&N) REPLACE(&R)
OPTION(*LSTDBG) /* OPTION(*EVENTF) */

Right click the member, Compile, Work with compile commands



------------------------------

--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
digest list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


End of WDSCI-L Digest, Vol 5, Issue 809
***************************************


--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.




------------------------------

--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
digest list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


End of WDSCI-L Digest, Vol 5, Issue 810
***************************************


--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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