Re: Accessing source members for editing in an IASP -- WDSCI-L

Mark,

here's what objects I have with that name...
QPWFSERVER  *PGM       QSYS      *PUBLIC                 *USE
QPWFSERVER  *JOBQ      QSYS     *PUBLIC                 *EXCLUDE
QPWFSERVER  *JOBD      QSYS     *PUBLIC                 *EXCLUDE
QPWFSERVER  *CLS        QSYS     *PUBLIC                 *USE
QPWFSERVER  *AUTL     QSYS     *PUBLIC                *USE

As you can see, public does have *use on the *autl

This is not an issue with accessing source members that reside in libraries
that reside in SYSBAS...

Just in an IASP

Brandon

"Mark Phippard" <MarkP@xxxxxxxxxxxxxxx> wrote in
message
news:OF11520527.41C8063D-ON85256D04.0054F13B-85256D04.005529CF@xxxxxxxxxxxxx
om...
> Brandon.
>
> This looks like another problem.  Check the QPWFSERVER *AUTL and see if
> *PUBLIC is *EXCLUDE.  If it is, you need to either change it to *USE or
> add something like QPGMR with *USE.
>
> This *AUTL is normally used to determine who has authority to browse the
> /QSYS.LIB file system via Windows Networking.  Apparently, the WDSC code
> to access members was getting tripped up by this.
>
> This has been fixed in 5.0.
>
> Mark
>
>
>
>
>
>
> "Brandon Wahl" <bwahl@xxxxxxxx>
> Sent by:
wdsci-l-bounces+markp=softlanding.com=Zwy7GipZuJhWk0Htik3J/w@xxxxxxxxxxxxxxx
g
> 04/10/2003 11:12 AM
> Please respond to Websphere Development Studio Client for iSeries
>
>         To:     wdsci-l@xxxxxxxxxxxx
>         cc:
>         Subject:        [WDSCI-L] Re: Accessing source members for editing
> in an IASP
>
>
> Don,
>
> I tried to access the source member in the IASP by changing my jobd but
> still didn't work... I'm now getting the following error: Message reported
> from file system: -1
>
> Before, I was getting an error: Message reported from file system: CPF3064
> Library XXXXXXXX not found.  where xxxxxxxxxx is the library I was trying
> to
> access.
>
>
> What I did was change my jobd to include the initial IASP and an initial
> libl that included the needed libraries....  am I missing something?
>
> Thanks Again,
> Brandon
>
>
> "Don Yantzi" <yantzi@xxxxxxxxxx> wrote in
> message
news:OF5A99D372.E381B002-ON85256D03.00689D21=r0JSptLoWH2LmzkN7vd/Rq1cXZ9k6wl
g@xxxxxxxxxxxxxxxx
> > Brandon,
> >
> > When WDSc retrieves lists and runs commands it uses the OS/400 remote
> > command server, but when it comes time to editing WDSc uses the OS/400
> DDM
> > server to read and write source members.  When you run the SETASPGRP
> > command it gets run in the remote command job, which does not affect the
> > DDM server job.  This is why the member can't be found.
> >
> > You can workaround this by setting the IASP in your job description
> which
> > will get picked up by both the remote command and DDM server jobs.
> >
> > Don Yantzi
> > WebSphere Development Studio Client for iSeries
> > IBM Toronto Lab
> > Phone: (905) 413-4476
> > IBM internal:  IBMCA(yantzi)  -  Internet:
> yantzi@xxxxxxxxxx
> >
> >
> >
> >
> >                       "Brandon Wahl"
> >                       <bwahl@xxxxxxxx>         To:
> wdsci-l@xxxxxxxxxxxx
> >                       Sent by:                 cc:
> >                       wdsci-l-bounces@x
> Subject:  [WDSCI-L] Accessing source members for editing in an IASP
> >                       idrange.com
> >
> >
> >                       09/04/2003 02:37
> >                       PM
> >                       Please respond to
> >                       Websphere
> >                       Development
> >                       Studio Client for
> >                       iSeries
> >
> >
> >
> >
> >
> > Anyone know of a way to access a source memeber for editing in WDSc 4.0
> > that's in an IASP?  I'm able to see source members in an IASP via remote
> > explorer, but can't edit....  have to run the setaspgrp command before I
> > can
> > see which makes sense, but pulling in the member for editing in lpex
> > doesn't
> > seem to be paying attention to previously run commands...
> >
> > Thanks,
> > Brandon
> >
> >
> >
> > _______________________________________________
> > 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.
> >
>
>
>
> _______________________________________________
> 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.
>