× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Rod,

The article says put the library name into the first 10 positions, and the member name into the next 10, so (for example):

chgdtaara %sst(*lda:1:10) &library
chgdtaara %sst(*lda:11:10) &mbrname

Kevin's right, though, make sure that you have the member in EVFEVENT in that library first. Hopefully the OPTION(*SRCDBG) is making that happen.

Good luck!

Dave Shaw
Mohawk Industries

----- Original Message ----- From: "Kevin Bucknum" <Kevin@xxxxxxxxxxxxxxxxxxx>
To: "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Sent: Wednesday, February 27, 2008 5:13 PM
Subject: Re: [WDSCI-L] Setting up a compile in WDSC...Another try


Do you have an EVFEVENT file in the library you compiled your program into? Does it have a member with the same name as your program? If so you just need to issue the correct CHGDTAARA commands to get that information in the LDA.

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of Rod Verity
Sent: Wednesday, February 27, 2008 4:04 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Setting up a compile in WDSC...Another try


>Rod,
>
>Hypothesis:
>
>CRTCBLPGM is OPM Cobol. To get the event file generated, in OPM RPG it's
OPTION(*SRCDBG). I'm guessing that Cobol is the same, and you >don't have
that option specified in your CRTCBLPGM command. Why don't you try that
and
see if it works?
>
>Good luck!
>
>Dave Shaw
>Mohawk Industries

Dave,
Thanks for your reply. I replaced *LSTDBG which we normally use with
*SRCDBG and apart from taking longer(not sure why), I still didn't receive
the error listing. It still seems to me I have to get the output file name
into the LDA according to the comment on page 2 in
http://www.itjungle.com/fhg/fhg080404-story01.html

I created a command called WDCBLCOMP which uses the CL program WDCBLCOMP.
Isn't that what this article says...that I have to get the output file
name
into the first 10 bytes of the LDA?

Thanks,
Rod

Please consider the environment before printing this email.

This message, including any attached documents, is intended for the
addressees only. It may contain information that is confidential,
privileged and/or exempt from disclosure. No rights to privilege or
confidentiality have been waived. Any unauthorized use or disclosure is
prohibited. If you have received this message in error, please reply to
the
sender by e-mail and delete or destroy all copies of this message.
______________________________________________________
Avant d'imprimer ce courriel, pensez à l'environnement.

Ce message, incluant tous les documents joints, est à l'intention des
destinataires visés seulement. Il peut contenir des renseignements
confidentiels, protégés et/ou ne pouvant pas être divulgués. Aucune
renonciation n'est faite quant à sa nature confidentielle et privilégiée.
Par conséquent, toute diffusion ou utilisation non autorisée est
strictement interdite. Si vous avez reçu ce message par erreur, veuillez
en aviser immédiatement l'expéditeur par retour de courriel et en détruire
toutes les copies existantes.

--
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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.