Well, I just went back and followed the screen-scrape.
It does ask me for the sbscript and piece.  I didn't realize that it
would be asking that in a pop-up box.  I thought that it would ask it
at the same time it asked for the field number etc.

Thanks everyone.
Kevin


On 9/29/05, chuck5566 <[EMAIL PROTECTED]> wrote:
> FWIW:  I seem to recall that to do this you also have to set DA(0)
> (or DA(1)) to the file number.
>
>
> On Sep 28, 2005, at 8:38 AM, Kevin Toppenberg wrote:
>
> > Yes I did it by hand.  And I think I have learned my lesson.  I don't
> > think I will do it again :-\
> >
> > Thanks
> > Kevin
> >
> > On 9/28/05, chuck5566 <[EMAIL PROTECTED]> wrote:
> >
> >> Kevin,  did you change the "global;piece" field by hand?
> >>
> >> I've changed that very same DD field a few times, by using Fileman to
> >> edit Fileman, which to me is geeky cool..  (A tip of the hat to
> >> George for making it possible, even as he cringes when anything does
> >> it.)
> >>
> >> Goes something like this:
> >>      S DIE="^DD(2005.2,"
> >>      S DA=22700
> >>      S DR="4"
> >>
> >>      D ^DIE
> >>
> >> I believe that if you make the change this way, FM takes care of the
> >> GL node (an x-ref?) for you.
> >>
> >> Chuck
> >>
> >>
> >>
> >> On Sep 27, 2005, at 10:03 PM, Kevin Toppenberg wrote:
> >>
> >>
> >>> OK, so I felt really stupid for shooting myself in the foot.  So I
> >>> figured out.
> >>>
> >>> It is stored in ^DD(2005.2,"GL",7,1,22700)
> >>> When I changed it to ^DD(2005.2,"GL",22700,1,22700), then everything
> >>> because consistent.
> >>>
> >>> I used my debugger to trace through the GLOBAL LISTING code and saw
> >>> what it was doing.
> >>>
> >>> Thanks anyway.
> >>> Kevin
> >>>
> >>>
> >>> On 9/27/05, Kevin Toppenberg <[EMAIL PROTECTED]> wrote:
> >>>
> >>>
> >>>> Trick/Quick question: Where all is the node;piece stored in the
> >>>> data dictionary?
> >>>>
> >>>> I ask because I think it is stored in two places, and I can only
> >>>> find
> >>>> one of them.
> >>>>
> >>>> I had added a field (#22700--my number space) to file 2005.2 using
> >>>> the
> >>>> screenman form method (mistake!).  Turns out that the screenman way
> >>>> doesn't allow one to specify the node to store data on.
> >>>>
> >>>> I then had the option of deleting the field and entering everything
> >>>> back in again.  I had written lengthy descriptions so wanted to
> >>>> avoid
> >>>> that if possible.
> >>>>
> >>>> I had not entered any actual data into the field, and had
> >>>> created no
> >>>> cross-references, so I thought that I could change its DD
> >>>> definition
> >>>> OK (you know about assumptions...).
> >>>>
> >>>> I found that $p(^DD(2005.2,22700,0),"^",4) = "7;1"
> >>>> I didn't want my data stored in note 7, so changed this to
> >>>> "22700;1"
> >>>>
> >>>> Now, when I use VPE data dictionary browser, it looks fine (shows
> >>>> 22700;1).  And when I go to enter data in with Fileman, it is
> >>>> fine--the file goes in, and when I come back to edit it again it is
> >>>> still there..
> >>>> But when I do I do an INQUIRE of the data I added, it doesn't show.
> >>>> And when I do the LIST FILE ATTRIBUTES, and in GLOBAL MAP listing
> >>>> format, it still shows the old "7;1"
> >>>>
> >>>> So apparently the node;piece is stored in more than one location.
> >>>> Any idea where the other location is?
> >>>>
> >>>> Thanks
> >>>> Kevin
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>> -------------------------------------------------------
> >>> This SF.Net email is sponsored by:
> >>> Power Architecture Resource Center: Free content, downloads,
> >>> discussions,
> >>> and more. http://solutions.newsforge.com/ibmarch.tmpl
> >>> _______________________________________________
> >>> Hardhats-members mailing list
> >>> Hardhats-members@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/hardhats-members
> >>>
> >>>
> >>
> >>
> >> -------------------------------------------------------
> >> This SF.Net email is sponsored by:
> >> Power Architecture Resource Center: Free content, downloads,
> >> discussions,
> >> and more. http://solutions.newsforge.com/ibmarch.tmpl
> >> _______________________________________________
> >> Hardhats-members mailing list
> >> Hardhats-members@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/hardhats-members
> >>
> >>
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by:
> > Power Architecture Resource Center: Free content, downloads,
> > discussions,
> > and more. http://solutions.newsforge.com/ibmarch.tmpl
> > _______________________________________________
> > Hardhats-members mailing list
> > Hardhats-members@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/hardhats-members
> >
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Hardhats-members mailing list
> Hardhats-members@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hardhats-members
>


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to