Using the IFS was Verifier Performance

Maybe by extension?
/myapplication/myversion/mysource/pgm1.rpgle
/myapplication/myversion/mysource/pgm2.clp
After all, look at the following, through the ifs:
WRKLNK '/QSYS.LIB/yoursourcelib.LIB/QRPGLESRC.FILE/*'
or in my case
WRKLNK '/QSYS.LIB/ROB.LIB/QPGMSRC.FILE/*'
And I'll get:
 and nothing there tells me what type the member is.  They are all just 
.MBR. 

To test this I opened a RPGLE member in browse mode in CODE.  I pasted 
that into NOTEPAD.  Then I did a file/Save as and saved it to this ifs 
directory:
//GDISYS/ROB/AA.RPGLE
(be sure to select all files and not just *.txt)

Then I opened up iSeries Navigator, opened up this system, Opened up File 
Systems, and drilled down to the /rob directory, and right clicked on 
aa.rpgle and several of the options there included:
CODE edit
CODE browse
CODE compile
CODE debug

I selected CODE edit.  Upon that I got an error that host system GDISYS 
was not defined.  I use the default of OS400.

I don't suppose anyone knows the short path to put in Code's File Open to 
get to IFS files, do they?

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Reeve Fritchman" <reeve@xxxxxxxxxx>
Sent by: code400-l-bounces@xxxxxxxxxxxx
02/26/2003 11:36 PM
Please respond to CODE/400 Discussion & Support
 
        To:     "'CODE/400 Discussion & Support'" <code400-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: Verifier Performance


What about the new IFS directory format ("Type 2"?) in V5R2?  I thought
supported some of the stuff necessary to make IFS source practical.  How
would CODE know which syntax checker to invoke if an IFS source file 
didn't
have a source type?

Then again, maybe I shouldn't ask...

> -----Original Message-----
> From: code400-l-bounces@xxxxxxxxxxxx
[mailto:code400-l-bounces@xxxxxxxxxxxx] On Behalf Of
> John Taylor
> Sent: Wednesday, February 26, 2003 11:20 PM
> To: CODE/400 Discussion & Support
> Subject: RE: Verifier Performance
> 
> Hi Reeve,
> 
> 
> > IBM has told us the communications manager is going to be improved;
that's
> > going to relate to how QZRCSRVS works for member locking and Verify
> > performance.  My guess is that we're not going to be seeing anything
until
> > the next OS/400 release unless the QZRCSRVS replacement is PTF'ed.  I
> > haven't heard of anything new in V5R2, so I'm assuming an
> > improvement is in
> > the future.
> 
> It seems to me that the biggest problem is not locking, but the sheer
number
> of QZRCSRVS jobs being cycled. As you're aware, starting a new job is a
> resource intensive operation in OS/400. When I verify, I can see dozens 
of
> these jobs being used, since each is only good for a single command. The
job
> runs for a fraction of a second before ending. It takes much longer to
start
> and end the job than it does to peform the work it was asked to do.
> 
> In fact, I'm truly wondering if there isn't something wrong with my
> configuration, because I'm having trouble believing that Code is 
supposed
to
> use QZRCSRVS as much as it's doing on my machine. That's got to be one 
of
> the worst ways to do client server on an AS/400, and I'm quite certain
that
> the Code team knows a lot more about writing a client server app than I
do.
> 
> 
> > This may not be much consolation, but the ability to compile from the
IFS
> > may be IBM's oblique solution to Verify performance; I haven't
> > experimented
> > with it because I'm still on V5R1.
> 
> I hope that's not the answer. I have so much code in PF-SRC members that
it
> would be a monstrous task to convert everything to stream files. 
Besides,
> what happens to the attributes (source type, member description) if you 
go
> to a stream file? Let me guess... we'd lose them in the name of
"progress".
> :)
> 
> 
> John Taylor
> 
> _______________________________________________
> This is the CODE/400 Discussion & Support (CODE400-L) mailing list
> To post a message email: CODE400-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/code400-l
> or email: CODE400-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/code400-l.
> 
> NOTE: WDSc for iSeries disucssion has it's own mailing list.
> Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l



_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/code400-l
or email: CODE400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.

NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at 
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l