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



Mike,
Those files will never be populated.
They are "format" file used to create the actual physical file in the DSPJRN 
command.
You can use them for creating your program, and then at runtime, override them 
to the actual file you want to use.
 


"Smith, Mike" <Mike_Smith@xxxxxxxxxxxxxxxx> wrote:
Don, Thanks for the reply. As I read your reply I started thinking
about what I was doing. I took off qualifying (qtemp) on my Select
statements and that resolved my initial compile issue. 
I'm definitely trying to avoid the 'ugly' so your point about using
QSYS/QADSPJRN or QSYS/QADSPJR4) is definitely worth looking at. Yours
was a very timely response-btw. 
However, I'm not sure I know how to use these files. I know when I do a
DSPAUDJRNE I get a bunch of QASYxxJ4 files populated, but what is going
to populate the files (QADSPJRN,QADSPJR4)???

Michael Smith
iSeries.mySeries.


-----Original Message-----
From: Donald Whittaker [mailto:donald_whittaker@xxxxxxxxx] 
Sent: Friday, November 11, 2005 12:38 PM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] Wdsc issues


You might try using the QSYS/QASYxxJE or QASYxxJ4
files (where xx = the journal entry type). Of course,
if you are using a _lot_ of journal entry types, this
gets ugly. If that is the case, consider using the
"generic" file (QSYS/QADSPJRN or QSYS/QADSPJR4) and
formatting the entry within the RPG program using the
QASYxxJE files as externally defined DS's.

For what it's worth...
Don Whittaker

--- "Smith, Mike" wrote:

> I thought about that David, and I might end up doing
> that. What I'm
> doing is a DSPAUDJRNE over numerous Audit Journal
> Types to do some
> reporting over the results.
> It just hit me this morning having a program relying
> on QTEMP causes
> issues with compiling in WDSC. 
> 
> Michael Smith
> iSeries.mySeries.
> 
> 
> -----Original Message-----
> From: David Gibbs [mailto:david@xxxxxxxxxxxx]
> Sent: Friday, November 11, 2005 10:00 AM
> To: Websphere Development Studio Client for iSeries
> Subject: Re: [WDSCI-L] Wdsc issues
> 
> 
> Smith, Mike wrote:
> > Second- and this might have a real simple
> workaround is. If I have a
> > RPGLE program that uses a file that is created in
> QTEMP, I can't get
> > it to compile.
> > In Green Screen, I run the CL that creates the
> Files, and then compile
> > the RPG. I can't seem to do this in WDSC.
> 
> How about creating a model database file in a normal
> library and compile
> against that. When you execute the program, dupe
> the model into qtemp
> and do an ovrdbf.
> 
> david
> --
> 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) 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.
> 





__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com

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.