× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. WDSCI-L
  3. October 2003

Re: WDSc - New Updates

Hi all,
I am on 5.01.  Is there a reason why I can't get the 5.1 updates when in
WDSc I select the New Updates option?  I keep getting 5.01 is available...
Shouldn't I be able to now see 5.1 to update to?  If not,  why not?

Regards,

Duie
(952) 918-4256


                                                                                
                                                        
                      wdsci-l-request@m                                         
                                                        
                      idrange.com              To:       wdsci-l@xxxxxxxxxxxx   
                                                        
                      Sent by:                 cc:                              
                                                        
                      wdsci-l-bounces@m        Subject:  WDSCI-L Digest, Vol 1, 
Issue 396                                               
                      idrange.com                                               
                                                        
                                                                                
                                                        
                                                                                
                                                        
                      10/30/2003 03:46                                          
                                                        
                      PM                                                        
                                                        
                      Please respond to                                         
                                                        
                      wdsci-l                                                   
                                                        
                                                                                
                                                        
                                                                                
                                                        




Send WDSCI-L mailing list submissions to
             wdsci-l@xxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
             http://lists.midrange.com/mailman/listinfo/wdsci-l
or, via email, send a message with subject or body 'help' to
             wdsci-l-request@xxxxxxxxxxxx

You can reach the person managing the list at
             wdsci-l-owner@xxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of WDSCI-L digest..."


Today's Topics:

   1. Re: Can't recover lost source member (Dave Cheng)
   2. RE: Can't recover lost source member (Chevalier, Rick)
   3. WDSc 5.1 (Wills, Mike N. (TC))
   4. Re: PDM User Options for CODE (craigs@xxxxxxxxx)
   5. RE: WDSc 5.1 (Jon Paris)
   6. RE: WDSc 5.1 (Nazmin Haji)
   7. RE: WDSc 5.1 (Wills, Mike N. (TC))
   8. RE: WDSc 5.1 (David McKnight)
   9. Re: Re: PDM User Options for CODE (Eric Simpson)


----------------------------------------------------------------------

message: 1
date: Thu, 30 Oct 2003 13:41:39 -0500
from: Dave Cheng <cheng@xxxxxxxxxx>
subject: Re: [WDSCI-L] Can't recover lost source member





Rick, is your losing source member situation reproducible?  If yes, can you
tell us the steps you do to make it happen?

Dave Cheng,
905-413-4063  cheng@xxxxxxxxxx




                      "Chevalier, Rick"

                      <Rick.Chevalier@ameri    To:  "WDSc Mailing List
(E-mail)" <wdsci-l@xxxxxxxxxxxx>
                      credit.com>              cc:

                      Sent by:                 Subject:  [WDSCI-L] Can't
recover lost source member
                      wdsci-l-bounces@midra

                      nge.com



                      10/30/2003 09:12 AM

                      Please respond to

                      Websphere Development

                      Studio Client for

                      iSeries






When trying to rename a source member in RSE the member disappeared.  The
best I can tell it was deleted.  I found a copy in the temp files folder
but I can't figure out how to get it back onto the iSeries.  I can look at
it in the jLPEX editor but saving it only places an empty member in my
library.

Can anyone help?

Rick Chevalier
AmeriCredit ITS
(817) 525-7178

_______________________________________________
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.





------------------------------

message: 2
date: Thu, 30 Oct 2003 13:40:25 -0600
from: "Chevalier, Rick" <Rick.Chevalier@xxxxxxxxxxxxxxx>
subject: RE: [WDSCI-L] Can't recover lost source member

It has been brought to my attention that we have not installed the host
portion of 5.1 yet.  We are also missing several PTF's.

At this point I am going to write it off to the missing host update and
PTF's and just be careful about renaming and copying members in RSE.  If
it happens after everything gets updated I'll reopen the thread.

Rick

> -----Original Message-----
> From: Dave Cheng [mailto:cheng@xxxxxxxxxx]
> Sent: Thursday, October 30, 2003 12:42 PM
> To: Websphere Development Studio Client for iSeries
> Subject: Re: [WDSCI-L] Can't recover lost source member
>
>
>
>
>
>
> Rick, is your losing source member situation reproducible?
> If yes, can you
> tell us the steps you do to make it happen?
>
> Dave Cheng,
> 905-413-4063  cheng@xxxxxxxxxx
>
>
>
>
>
>                       "Chevalier, Rick"
>
>                       <Rick.Chevalier@ameri    To:  "WDSc
> Mailing List (E-mail)" <wdsci-l@xxxxxxxxxxxx>
>                       credit.com>              cc:
>
>                       Sent by:                 Subject:
> [WDSCI-L] Can't recover lost source member
>                       wdsci-l-bounces@midra
>
>                       nge.com
>
>
>
>
>
>                       10/30/2003 09:12 AM
>
>                       Please respond to
>
>                       Websphere Development
>
>                       Studio Client for
>
>                       iSeries
>
>
>
>
>
>
>
>
> When trying to rename a source member in RSE the member
> disappeared.  The
> best I can tell it was deleted.  I found a copy in the temp
> files folder
> but I can't figure out how to get it back onto the iSeries.
> I can look at
> it in the jLPEX editor but saving it only places an empty member in my
> library.
>
> Can anyone help?
>
> Rick Chevalier
> AmeriCredit ITS
> (817) 525-7178
>
> _______________________________________________
> 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.
>



------------------------------

message: 3
date: Thu, 30 Oct 2003 14:23:07 -0600
from: "Wills, Mike N. (TC)" <MNWills@xxxxxxxxxxxxxx>
subject: [WDSCI-L] WDSc 5.1

My complements to the IBM developers. In my initial hour of using it, I
like
it better than 5.

I have a question: How do I have it prompt me for field names in other
spots
besides on bifs?


Mike Wills
Lawson Programmer/Administrator
Taylor Corporation
Email: mnwills AT taylorcorpNOSPAM DOT com
AIM: iSeriesCodePoet


------------------------------

message: 4
date: Thu, 30 Oct 2003 15:35:04 -0500
from: craigs@xxxxxxxxx
subject: [WDSCI-L] Re: PDM User Options for CODE





You probably want to have the lock and sequence numbers at the end.
CODEEDIT has the lock options that CODEBRWS does not.  There is a
discussion of this on the CODE thread of midrange.com.  That is probably
more appropriate there anyway.
Here are the comments in my wrapper program:
For EVFCFDBK, there are 4 parms.  The first 3 parms are required.
Parm 4 (CODEPARM) values:
Browse source = 'CODEBRWS "<>&L/&F(&N)" /N'
   Design DDS = 'CODEDSU "<>&L/&F(&N)"'
  Edit source = 'CODEEDIT "<>&L/&F(&N)" /M Y /N'
The empty <> looks for the first server (or enter a server here).
/M Y means to lock the member.
/N indicates to retain sequence numbers.

Your call would be of the form:

 call qcode/evfcfdbk parm('37' 'Y' 'OS400' '<LOCAL> CODEEDIT "<>&L/&F(&N)"

 /M Y /N')





Then just substitute the above options in place of CODEEDIT...
I have written a program that accepts parms to call this EVFCFDBK.  The
main function is to set a current library specified for that user in a file
to ensure everyone runs this with a unique current library.  I did the same
thing wrapping the STRCODE command in a wrapper setting a current library
beforehand.  If you do not have a unique current library set during the
STRCODE, your souce could appear on someone else's workstation.  I have
seen this before.

Craig Strong

** Phil wrote:

 Chris:


    Option  . . . . . . . . :   CE

    Command . . . . . . . . :   CALL PGM(Qdevtools/EVFCFDBK) PARM('37' 'Y'

 'OS400'

   '<LOCAL> CODEEDIT "<OS400>&l/&f(&n)"')


 For browse, change CODEEDIT to CODEBRWS.


 Phil







------------------------------

message: 5
date: Thu, 30 Oct 2003 15:40:12 -0500
from: "Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx>
subject: RE: [WDSCI-L] WDSc 5.1

 >> I have a question: How do I have it prompt me for field names in other
spots besides on bifs?

Yup - just hit Ctrl + space pretty much at any time.

Jon Paris
Partner400
www.Partner400.com




------------------------------

message: 6
date: Thu, 30 Oct 2003 15:56:35 -0500
from: Nazmin Haji <haji@xxxxxxxxxx>
subject: RE: [WDSCI-L] WDSc 5.1





You want to make sure that you have created an outline view first. Ctrl +
space uses the information from the outline view to display fields defined
in the program.

Regards,
Nazmin Haji



------------------------------

message: 7
date: Thu, 30 Oct 2003 15:00:48 -0600
from: "Wills, Mike N. (TC)" <MNWills@xxxxxxxxxxxxxx>
subject: RE: [WDSCI-L] WDSc 5.1

That doesn't seem to work in /free.



Mike Wills
Lawson Programmer/Administrator
Taylor Development
Email: mnwills@xxxxxxxxxxxxxx
Direct Line: (507) 625-3187

-----Original Message-----
From: Jon Paris [mailto:Jon.Paris@xxxxxxxxxxxxxx]
Sent: Thursday, October 30, 2003 2:40 PM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] WDSc 5.1

 >> I have a question: How do I have it prompt me for field names in other
spots besides on bifs?

Yup - just hit Ctrl + space pretty much at any time.

Jon Paris
Partner400
www.Partner400.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.


------------------------------

message: 8
date: Thu, 30 Oct 2003 16:40:09 -0500
from: David McKnight <dmcknigh@xxxxxxxxxx>
subject: RE: [WDSCI-L] WDSc 5.1





It should work within /free blocks.   Content assist may or may not show up
depending on the context.   For example, if there are no completions for a
particular opcode or if the cursor is in comments then you will not see
anything.  Do you see any difference if the /free is specified as "c/free"
versus " /free"?

____________________________________
David McKnight
Phone:   905-413-3902 , T/L:  969-3902
Internet: dmcknigh@xxxxxxxxxx
Mail:       D1/643/8200/TOR
____________________________________



|---------+---------------------------->
|         |           "Wills, Mike N.  |
|         |           (TC)"            |
|         |           <MNWills@taylorco|
|         |           rp.com>          |
|         |           Sent by:         |
|         |           wdsci-l-bounces@m|
|         |           idrange.com      |
|         |                            |
|         |                            |
|         |           30/10/2003 04:00 |
|         |           PM               |
|         |           Please respond to|
|         |           Websphere        |
|         |           Development      |
|         |           Studio Client for|
|         |           iSeries          |
|         |                            |
|---------+---------------------------->

>------------------------------------------------------------------------------------------------------------------------------|

  |
|
  |       To:       Websphere Development Studio Client for iSeries
<wdsci-l@xxxxxxxxxxxx>                                       |
  |       cc:
|
  |       Subject:  RE: [WDSCI-L] WDSc 5.1
|
  |
|
  |
|

>------------------------------------------------------------------------------------------------------------------------------|




That doesn't seem to work in /free.



Mike Wills
Lawson Programmer/Administrator
Taylor Development
Email: mnwills@xxxxxxxxxxxxxx
Direct Line: (507) 625-3187

-----Original Message-----
From: Jon Paris [mailto:Jon.Paris@xxxxxxxxxxxxxx]
Sent: Thursday, October 30, 2003 2:40 PM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] WDSc 5.1

 >> I have a question: How do I have it prompt me for field names in other
spots besides on bifs?

Yup - just hit Ctrl + space pretty much at any time.

Jon Paris
Partner400
www.Partner400.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.





------------------------------

message: 9
date: Thu, 30 Oct 2003 16:45:45 -0500
from: Eric Simpson <esimpson@xxxxxxxxxx>
subject: Re: [WDSCI-L] Re: PDM User Options for CODE





Craig,

You don't need the /N or /M Y options.  We automatically lock the member
when you use CODEEDIT and automatically retain sequence numbers for
CODEBRWS and CODEEDIT.

Eric Simpson
WebSphere Development Studio Client, IBM Toronto Lab, D1/140/8200/MKM
Phone:  (905) 413-3226,  T/L:  969-3226,  Fax: (905) 413-4850,  Email:
esimpson@xxxxxxxxxx



|---------+---------------------------->
|         |           craigs@xxxxxxxxx |
|         |           Sent by:         |
|         |           wdsci-l-bounces@m|
|         |           idrange.com      |
|         |                            |
|         |                            |
|         |           10/30/2003 03:35 |
|         |           PM               |
|         |           Please respond to|
|         |           Websphere        |
|         |           Development      |
|         |           Studio Client for|
|         |           iSeries          |
|         |                            |
|---------+---------------------------->

>---------------------------------------------------------------------------------------------------------------------------------------------|

  |
|
  |       To:       wdsci-l@xxxxxxxxxxxx
|
  |       cc:
|
  |       Subject:  [WDSCI-L] Re: PDM User Options for CODE
|
  |
|
  |
|

>---------------------------------------------------------------------------------------------------------------------------------------------|








You probably want to have the lock and sequence numbers at the end.
CODEEDIT has the lock options that CODEBRWS does not.  There is a
discussion of this on the CODE thread of midrange.com.  That is probably
more appropriate there anyway.
Here are the comments in my wrapper program:
For EVFCFDBK, there are 4 parms.  The first 3 parms are required.
Parm 4 (CODEPARM) values:
Browse source = 'CODEBRWS "<>&L/&F(&N)" /N'
   Design DDS = 'CODEDSU "<>&L/&F(&N)"'
  Edit source = 'CODEEDIT "<>&L/&F(&N)" /M Y /N'
The empty <> looks for the first server (or enter a server here).
/M Y means to lock the member.
/N indicates to retain sequence numbers.

Your call would be of the form:

 call qcode/evfcfdbk parm('37' 'Y' 'OS400' '<LOCAL> CODEEDIT "<>&L/&F(&N)"

 /M Y /N')





Then just substitute the above options in place of CODEEDIT...
I have written a program that accepts parms to call this EVFCFDBK.  The
main function is to set a current library specified for that user in a file
to ensure everyone runs this with a unique current library.  I did the same
thing wrapping the STRCODE command in a wrapper setting a current library
beforehand.  If you do not have a unique current library set during the
STRCODE, your souce could appear on someone else's workstation.  I have
seen this before.

Craig Strong

** Phil wrote:

 Chris:


    Option  . . . . . . . . :   CE

    Command . . . . . . . . :   CALL PGM(Qdevtools/EVFCFDBK) PARM('37' 'Y'

 'OS400'

   '<LOCAL> CODEEDIT "<OS400>&l/&f(&n)"')


 For browse, change CODEEDIT to CODEBRWS.


 Phil





_______________________________________________
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)
digest 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.


End of WDSCI-L Digest, Vol 1, Issue 396
***************************************

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service.






________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.