How many Line a DCL can manage on VMS 5.5

[Hein van den Heuvel]

You have a handful of 'labels' that have a space between the intended label name and the colon to make it a label.
For example: $ STOCKNEG_MX :
And several more of those STOCK thingies.
Fix that!
It might not cuase this problem, but it should be cleaned up. See '$HELP GOSUB'


GOSUB
Parameter
label

Specifies a label of 1 to 255 alphanumeric characters that
appears as the first item on a command line. A label may not
contain embedded blanks. When the GOSUB command is executed,
control passes to the command following the specified label.

The label can precede or follow the GOSUB statement in the
current command procedure. When you use a label in a command
procedure, it must be terminated with a colon (:). If you use
duplicate labels, control is always given to the label most
recently read by DCL.



Hein.

[Wim Van den Wyngaert]

Hein,

I don't like it but labels may have spaces before the :. Test it.

Wim

[labadie_1]

Wim

yes of course, a system manager must know Dcl, but some others langages are much more efficient when doing specific things: for string manipulation, Perl, awk ( SYS$COMMON:[SYSHLP.EXAMPLES.tcpip.snmp]gawk ), for others things, Python...

And I think Hein will not disagree that Perl is helpful :-)

[Wim Van den Wyngaert]

Labadie,

of course Perl is OK but my point is that the ONLY standard is DCL. What would you say if I used POSIX ksh as a scripting language on VMS and you don't know ksh but you have to manage systems created by me ?

Second point is that DCL runs on every VMS node, whatever the version.

And is very readable.

Wim

[Jan van den Ende]

Gerard,

I tend to heavily agree with Wim!!!

In the past I HAVE run into a site where 'everything' was in Fortran.

In itself that would not have to pose a big problem, but if you need to change something and nobody around knows IF the sources are still there, let alone where...
Rather frustrating if they have just purchased a nice new Vax with RA81's, and all system management procedures and user program control procedures reference DRA0, DRB0, DRC0 and DRD0....

Jan

[labadie_1]

Wim

I think we agree that code must be easily maintained. Awk is (I think since Tcpip 5.0) on any Vms system, in this bizarre place. This adds regular expressions, that Dcl lacks in some circumstances.

[Wim Van den Wyngaert]

Furthermore,

compilers require licenses require money (we have fortran and pascal and some c)

perl is freeware and requires someone of good will to correct the problems/support it on new versions

and ...

DCL is included and supported.

Wim

[labadie_1]

Jan

>>>In itself that would not have to pose a big problem, but if you need to change something and nobody around knows IF the sources are still there, let alone where...

Of course, if the source is not here, and of course with Dcl the source is always here :-)


>>>Rather frustrating if they have just purchased a nice new Vax with RA81's, and all system management procedures and user program control procedures reference DRA0, DRB0, DRC0 and DRD0....

yes, but this leads more to the knowledge (or absence of) about logical names, than about the preferred langage on the site

:-)

[Jan van den Ende]

Gerard,


yes, but this leads more to the knowledge (or absence of) about logical names, than about the preferred langage on the site


I am kind of a 'software nomad', so I get around (current assignment rather long-lasting, though).
And you find what you find, and have to make do with that.
But IF there is no good knowledge/usage of logical names (and I am on record in this forum as a true advocate, even more especially Concealed Logical names), then compiled languages certainly DO complicate matters.

All in all, I prefer DCL.


Jan

[Bui_2]

Ok my problem are sovlved,

the develloper's cell simply forget an ENDIF, and VMS getback a label -W- and not an error with IF-THEN-ELSE loop

thanks all this problem my muched learn