Thanks John for this education
Kris Buelens,
--- VM/VSE consultant, Belgium ---
---
Op ma 28 nov. 2022 om 13:45 schreef John P. Hartmann :
> On 11/28/22 11:10, Kris Buelens wrote:
> > I repeat that #1 (or in France £1)
On 11/28/22 11:10, Kris Buelens wrote:
I repeat that #1 (or in France £1) is a counter, so no spaces by
definition.
This is no longer the case.
Counters can now contain non-numeric strings as well as proper numbers.
Perhaps #1 should be called a variable, just as Alain does.
The initial
On 11/28/22 10:07, Alain Benvéniste wrote:
Yes John ^ is the good character.
There is something i still don’t understand :
If i code
If £1==a
and a is equal to b3339
b for blank, the if is not honored
If I use a
If space(£1)==space(a) it works.
It could mean that when i do a set £1:=a the blank
I repeat that #1 (or in France £1) is a counter, so no spaces by
definition.
I guess that space(#1) converts it to a string and so you can compare to
identifier "a", what is a string
Kris Buelens,
--- VM/VSE consultant, Belgium ---
Yes John ^ is the good character.
There is something i still don’t understand :
If i code
If £1==a
and a is equal to b3339
b for blank, the if is not honored
If I use a
If space(£1)==space(a) it works.
It could mean that when i do a set £1:=a the blank is removed… ?
Resiliency Services on Z
On 11/27/22 13:51, a.benveni...@free.fr wrote:
Sorry John to come back but,
There is no /== operator in specs.
For me, ^== works as the not exactly equal operator because my terminal
emulator maps ^ to not; perhaps it works for you too. Otherwise you
need to find the not character on your
Sorry John to come back but,
With
"! SPECs",
" a: 54.5 .",
" if (£1/==a) then",
" set £1:=a",
" set £2:=1",
" else",
" set £2+=1",
" endif",
and with 6010A or 60102 and by reducing or not my storage from 128M to 16M I
receive :
FPLYAC1434E Parse error in state 145,
On 11/27/22 12:39, a.benveni...@free.fr wrote:
" if (£1/=a) then",
The numerically not equal operator converts both arguments to numbers
and then performs a numeric compare.
Your compare of 6010A fails because the digit A is not decimal. (Specs
has no facility to compare hexadecimal.)
Rob, I would pleased to run it !
De : CMS/TSO Pipelines Discussion List
de la part de Rob van der Heij
Date : dimanche, 27 novembre 2022 à 10:06
À : cms-pipeli...@listserv.meduniwien.ac.at
Objet : Re: IF testing characters
While this doesn't address your questions about SPEC, I do have a
Yes John !
But now, back with a simplified code,
[code]
"! SPECs",
" a: 54.5 .",
" if (£1/=a) then",
" set £1:=a",
" set £2:=1",
" else",
" set £2+=1",
" endif",
" 1-* 1",
" print £2 picture 9 nextword",
"!> $$TEMP$$ $$TEMP$$ A3"
a: value can be 60102, 30051 but
While this doesn't address your questions about SPEC, I do have a very
interesting pipeline that uses almost all options of LOOKUP to go through a
User Directory and determine gaps or re-allocate minidisks from one (or
all) volumes to new volumes to generate DIRMAINT commands...
Rob
The else clause is never executed because you unconditionally assign
counters 1 through 5 at the beginning of each cycle. Perhaps you should
delete the first five assignments. Or use if first() to initialise
counters.
On 11/26/22 14:44, a.benveni...@free.fr wrote:
The last test I did do
The last test I did do not send any error message but £4 and £5 are not
incremented as it is supposed based on the if :
>From the q da details command :
a is the cyls value
b is the serial number value
c is the ssid value
"! SPECs",
" a: 54.5 .",
" b: 67.10 .",
" c: 85.4 .",
" set £1:=a",
"
On 11/26/22 13:15, Alain Benvéniste wrote:
So there no syntax to assign characters to a variable to test it through a if ?
Sure there is:
if (#56 -= 1) then ...
(decrement counter 56 and test for 0 or nonzero.)
Perhaps it would be easier if you set your terminal/emulator to the US
code
! is the vertical bar (|) on most European terminals. It would have
been nice to know the actual error message.
On 11/26/22 12:14, Kris Buelens wrote:
I don't understand what these
are supposed to do
I think there’s the /= for “not equal” numeric, and /== for when it’sa
string.
Rob
On Sat, 26 Nov 2022 at 13:15, Alain Benvéniste wrote:
> It is just things i tested…
> I suspect…. £ is # like @ is à…
> So there no syntax to assign characters to a variable to test it through a
> if ?
>
>
>
It is just things i tested…
I suspect…. £ is # like @ is à…
So there no syntax to assign characters to a variable to test it through a if ?
Resiliency Services on Z Mainframe
alain.benveni...@kyndryl.com
> Le 26 nov. 2022 à 12:24, Kris Buelens a écrit :
>
> This doesn't read very well here
This doesn't read very well here
" set £1=''",
I guess £1 stands for #1 outside the UK, and I don't understand what these
are supposed to do
Ignoring it would mean you try to assign counter 1 to an empty
string. It are counters, hence only accept numeric values
Kris Buelens,
Hi,
I try to compare characters fields (a, b and c) in the if using this way and
the concatenation.
Both cases send me a error msg.
The sets seem ok, but when testing them in the if it looks to me I use a wrong
syntax...
"! SPECs",
" a: 54.5 .",
" b: 67.10 .",
" c: 85.4 .",
" set
19 matches
Mail list logo
