|
midrange.com
Haven't tried, but i'm guessing the end result will be the same (won't
trigger anything related to the validity check). What's interesting to me
though, is within WDSC I think the programmer is actually using what looks
to be the CPYSRCF command, the server job servicing the WDSC session also
mentions something like 'CLIENT REQUEST - CPYSRCF' or something similar.
Not complaining, just wondering how things work. It almost looks like
there's some sort of 'engine' that's packaging the request rather than
touching the actual CL command.
The programmer also just mentioned that even when coding a CL (on the
greenscreen) and prompting the CPYSRCF command it triggers the checker (he
was creating a test CL to see how the CPYSRCF behaved differently in
batch/interactive). When running it in batch it failed the CPYSRCF command
because it was unable to use items in the display file. When run
interactively it (of course) triggered the checker.
Sarah Poger
Gladstone
<listmember@glads To
tone.info> Websphere Development Studio Client
Sent by: for iSeries <wdsci-l@xxxxxxxxxxxx>
wdsci-l-bounces@m cc
idrange.com
Subject
Re: [WDSCI-L] Validity Checks
02/06/2006 02:27
PM
Please respond to
Websphere
Development
Studio Client for
iSeries
<wdsci-l@midrange
.com>
Chad-
Just curious, what happens when you use iSeries Navigator to copy a
source member into/out of a production source library? Or an FTP
client?
-Sarah
On 2/6/06, ChadB@xxxxxxxxxxxxxxxxxxxx <ChadB@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> That's it in a nutshell, but i'd think that WDSC would do something other
> than 'ignore' it...
>
> This is all very new to me and we're just looking to find out the impact
of
> moving our programmers from greenscreen to WDSC.
>
>
> Mark Phippard
> <markp@softlandin
> g.com> To
> Sent by: Websphere Development Studio Client
> wdsci-l-bounces@m for iSeries <wdsci-l@xxxxxxxxxxxx>
> idrange.com cc
>
> Subject
> 02/06/2006 01:36 Re: [WDSCI-L] Validity Checks
> PM
>
>
> Please respond to
> Websphere
> Development
> Studio Client for
> iSeries
> <wdsci-l@midrange
> .com>
>
>
>
>
>
>
> wdsci-l-bounces@xxxxxxxxxxxx wrote on 02/06/2006 01:30:48 PM:
>
> > In some of our initial 'playing around' with WDSC 6 and RSE, we're
> noticing
> > that when copying source from/to one of our production source
> libraries,
> > that the existing validity checking doesn't seem to be triggered.
It's
> > almost like it's not really touch the actual 'cpysrcf' command or is
> just
> > ignoring the validy check portion of the command.
> >
> > We're using some very basic change management that just enforces the
> > checking out/in of production source and helps with the auditing of
> these
> > functions. (The validity checker calls a program when source is copied
> > from/to certain libraries and the programmer must log info pertaining
to
> > project, etc.). Is anyone doing something similar in the WDSC
> environment
> > or is it necessary to get into more of a full blown product that helps
> with
> > change management. We're hoping for a simple method like we're using
> > now...
>
> So are you saying you have attached a validity checker to CPYSRCF, and
> this pops-up a dialog asking for information about the copy? That isn't
> going to work in a graphical environment, there is no way for you to
bring
> a screen up.
>
> Mark
>
>
>
_____________________________________________________________________________
>
> Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM
> Email Security Management Services powered by MessageLabs.
>
_____________________________________________________________________________
>
> --
> 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.
>
>
_____________________________________________________________________________
>
> Scanned by IBM Email Security Management Services powered by MessageLabs.
> For more information please visit http://www.ers.ibm.com
>
_____________________________________________________________________________
>
>
> ForwardSourceID:NT0003A902
>
>
_____________________________________________________________________________
> Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
>
_____________________________________________________________________________
>
> --
> 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.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
ForwardSourceID:NT0003A97E
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs. For
more information please visit http://www.ers.ibm.com
_____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
