RE: Library and Source File Question

[Vernon Hamberg <vhamberg@xxxxxxxxx>]

Inline

At 12:20 PM 10/14/02 -0500, you wrote:
> PDM doesn't edit anything.  It's what you call from PDM that does.
Of course not - what I meant is that PDM has no options (from IBM) to
handle IFS. One of the beauties of PDM is the correlation of source type
with create command.

Has IBM given any suggestions on using RPG source in the IFS? If not, I
still don't see the point of putting RPG code there. I'll need to see some
real benefit to this.

> If you use Operations navigator and right click on an item, let's say
> /rob/mypgm.txt, one of the options is CODE edit.  Yet another 'unfeature'
> of SEU.
Interesting. But I don't think this is a feature of CODE, rathe, it's the
behavior of Windows. WDSC associates CODE with extensions that match the
normal source types, so any file with .c will be handled by CODE, whether
local or on a 400. And this is what makes it possible to edit with CODE if
you work from WDSC iSeries projects, which don't explicitly list "CODE
Edit", but that is what gets called for .c files. .h extensions do not, as
that is not a 400 source type.

It did not work in my V5R1 from within OpsNav. I.e., from File
Systems->Integrated File Systems. I had to go through File Systems->File
Shares and open up the root share I've created. It seems v5r2 has improved
on this, so that extensions in IFS will get processed according to Windows
file associations. This is very cool.

But it did nothing for members of source files, which have the .mbr
extension. Unless there have been othere file associatiosn established on
your machine. Nice idea, seems to me.

Cheers

Vern

> Rob Berendt
> --
>
> vhamberg@attbi.com
>         Subject:        RE: Library and Source File Question
>
> PDM
> won't touch it, unless there's a V5R2 improvement. WDSC
> (SP2) treats it differently than source physicals, too.
> I just saw today that a .c source file did not have the
> Open with CODE option when right-clicking it in the IFS
> subsystem. If it were in a physical with member type C,
> the CODE option would've been there.