RE: FW: IFS symbolic link library mapping

Can you open it with the database function of iSeries Navigator?  You 
might be pleasantly surprised with that. 

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




"Uros Davidovic" <Uros_Davidovic@xxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
04/11/2003 09:31 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     "'Midrange Systems Technical Discussion'" 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: FW: IFS symbolic link library mapping


Vern,

I think you hit it right on the head, that is my problem, I am trying to
look at a PF created through DDS. In fact, the only reason I set this up
is to do that, so I guess I will end up either copying into a flat file
or a stream file. FYI, tried to open with both Notepad and EditPlus and
UltraEdit.

Thanks!
Uros

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vern Hamberg
Sent: Friday, April 11, 2003 10:12 PM
To: Midrange Systems Technical Discussion
Subject: Re: FW: IFS symbolic link library mapping


Tried a couple things - I have a share to the root ('/') that has the 
simple conversion and 'mbr' for extension - don't have the period in
front, 
but it is not supposed to matter - I think.. I created a symbolic link
in 
the root to my library, VERN. Then I opened Windows Explorer to that
link 
and see all my objects in that library. If I double-click a file, it
opens 
up the member list. I was able to open one in TextPad - looked fine.
Also, 
as we have CODE, a right-click on the member has CODE Edit as an option.

I closed TextPad and created a share to the link itself. Got to the
member 
list and right-click, then took CODE edit - made a change, exited and
saved 
the member. Again, worked fine.

There is an exception - it works only with source physicals or 
non-externally-described data physicals - files created with CRTPF 
RCDLEN(nnn) will work.

This was to a V5R1 machine that is at CUME 3007 and pretty good on PTFs.

What does it mean when you say "it comes up"? What application are you 
using to open it?

BTW, I have found that editing source members in Windows when they have 
been accessed with NetServer can be a problem - I've even lost all the 
contents. You have to be sure not to have any lines longer than the 
record-length or SRCDTA field-length, for one thing. It's not a
procedure 
we trust anymore.

HTH

Vern

At 08:55 PM 4/11/2003 -0400, you wrote:
>Posted this yesterday, just wanted to see if I will have better luck 
>today with someone answering...
>
>Thanks. FYI, I get a message that says "Incorrect function" and has the

>file location when I try to specify auto conversion and try to open a 
>file.
>
>
>-----Original Message-----
>From: midrange-l-bounces@xxxxxxxxxxxx 
>[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Uros Davidovic
>Sent: Thursday, April 10, 2003 9:55 PM
>To: 'Midrange Systems Technical Discussion'
>Subject: IFS symbolic link library mapping
>
>
>Created a symbolic lynk to a library on the as400 in the IFS root. 
>Added a netshare. Tried several text conversion options (simple, with 
>.mbr extension being automatic), no conversion (obviously did not 
>work). If I have no conversion, the file comes up in the EBCDIC 
>version, if I specify a conversion with CCSID 0, any attempt to open 
>results in a message "Incorect function". Any ideas or will I have to 
>do a CPYTOSMTF? CCSID 37 does not appear to be an option on the CCSID 
>drop down in the netserver share setup screen.


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


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