× 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,

Commands look right. You can try a dspdtaara *lda output(*print) from the command prompt and check the printout to see if it's working. If that's okay, then something else must be the problem, but I'm out of ideas for what to look for tonight. Maybe someone else will pipe up with something.

Dave Shaw
Mohawk Industries

----- Original Message ----- From: "Rod Verity" <rod_verity@xxxxxxxxxxxxxx>
To: <wdsci-l@xxxxxxxxxxxx>
Sent: Wednesday, February 27, 2008 5:41 PM
Subject: Re: [WDSCI-L] Setting up a compile in WDSC...Another try



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

Dave,
Yes the EVFEVENT file(pgmname.mbr) is created in the output
library(which is different one than the input library). This was being
created with the *LSTDBG option also. I can go to that file and select Show
in Error List but it won't automatically display. I was already doing the
following two commands after the CRTCBLPGM:
CHGDTAARA DTAARA(*LDA (1 10)) VALUE(&OBJLIB)
CHGDTAARA DTAARA(*LDA (11 10)) VALUE(&PGM)

I got this out of some help info. Is this the wrong command from a CL
program?

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.