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



Oh, and I am kind of glad that 
dcl &varname *dec (9 0)
does not get through the prompter.  I do a lot of lines intentionally like 
that and I hate it when someone prompts it to make it ugly.  For example I 
find this much easier to read:
    DCL  &TAPEDRIVE   *CHAR  10  /* Tape drive to process            */
    DCL  &MSG         *CHAR 132  /* First level message text         */
    DCL  &MSGDTA      *CHAR 132  /* Message data                     */
    DCL  &MSGID       *CHAR   7  /* Message id                       */
    DCL  &VOLID       *CHAR  14  /* Volume id of the tape            */
    DCL  &PREFIX      *CHAR   1  /* Prefix of the requested tape vol */ +
                                 /* A = ADSM, or old TSM             */ +
                                 /* D = Domino backup on GDIHQ       */ +
                                 /* G = GDI                          */ +
                                 /* H = GDIHQ DB2                    */ +
                                 /* S = GDISYS                       */ +
                                 /* W = GDWEB                        */
Than this:
             DCL        VAR(&TAPEDRIVE) TYPE(*CHAR) LEN(10) /* Tape + 
                          drive to process            */ 
             DCL        VAR(&MSG) TYPE(*CHAR) LEN(132) /* First + 
                          level message text         */ 
             DCL        VAR(&MSGDTA) TYPE(*CHAR) LEN(132) /* Message +
                          data                     */ 
             DCL        VAR(&MSGID) TYPE(*CHAR) LEN(7) /* Message + 
                          id                       */ 
             DCL        VAR(&VOLID) TYPE(*CHAR) LEN(14) /* Volume id +
                          of the tape            */ 
             DCL        VAR(&PREFIX) TYPE(*CHAR) LEN(1) /* W = + 
                          GDWEB                        */ 

But, the above did get through my WDSC prompter.  And it wasn't quite as 
ugly as when I did this through the SEU prompter for all those who miss 
the god awful way that SEU formatted commands.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Vernon Hamberg <vhamberg@xxxxxxxxxxx> 
Sent by: wdsci-l-bounces@xxxxxxxxxxxx
05/09/2005 10:29 PM
Please respond to
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>


To
Websphere Development Studio Client for iSeries <wdsci-l@xxxxxxxxxxxx>
cc

Subject
Re: [WDSCI-L] cl prompting






There are a lot of problems with the CL prompter. Some were caused by 
5.1.2.4. Others, like this one, just don't work. Better than SEU? NOT!

Yet, the developers are aware of some of these things. The prompter 
originated as a command-line prompter, not a programming prompter with 
variable names and expressions - I dare you to put something in with *CAT 
- 
and something as simple as

dcl &varname *dec (9 0)

does not get through the prompter correctly. These are things that are 
second-nature in SEU, and the fact they don't work here makes this a tough 

sell.

BTW, if there are no parameters on a command (such as ENDDO), you cannot 
prompt it. Sheesh! And there are several cases where prompting does not 
capitalize things that are not in quotes - not even *CAT operators, e.g. 
Again, please give us something as good as SEU - this ain't it yet! Either 

do it everywhere (as SEU does) or not at all.

I rant - all you developers have heard me before - I bet you won't get the 

time you need to really make this work. More's the pity. But maybe you can 

point out to the money folks that IBM has all this hype and promise, and 
that this, at least, does not live up to the promise - IMO, anyway.   ;-)

Vern

At 12:25 PM 5/9/2005, you wrote:

>Reading along with the new wdsc redbook, I'm trying out the cl formatter.
>I prompted a cmd and realized that the variable name can't be longer than
>the length of the PARM on the command!  And, that the variable name can 
be
>as long as the PARM - i.e. over 10.
>
>Guess I'll skip to the next chapter.
>
>Version: 5.1.2.4
>Build id: 20050104_2139
>
>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) 
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.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.