Hi Mike,
that was also my analysis...
Many thanks and regards
Yves
Please don't try to analyze the dump - I did it already - this is not really my
problem
I would be interested:
- what did IBM change in TLD - CB not documented?
- will this change make problems in other software?
- do someone (???) have the source?
Thanks to all of you
Best regards
Yves
On 12/19/23 20:12:56, Joseph Reichman wrote:
The definition of the macro was before a CSECT was established the macro module
from file192 established a CSECT
When I established a CSECT before the macro definition the picked it up
.
Does the following do what you expect? Otherwise, what?
On 12/19/23 20:12:56, Joseph Reichman wrote:
The definition of the macro was before a CSECT was established the macro module
from file192 established a CSECT
When I established a CSECT before the macro definition the picked it up
.
I don't see your code.
"file192"?
I believe it's quite
The definition of the macro was before a CSECT was established the macro module
from file192 established a CSECT
When I established a CSECT before the macro definition the picked it up
> On Dec 19, 2023, at 10:07 PM, Paul Gilmartin
> <0014e0e4a59b-dmarc-requ...@listserv.uga.edu> wrote:
>
On 12/19/23 17:53:53, Joe Reichman wrote:
The macro was invoked in the context of unnamed csect However the Macro established
CSECT would having a macro Whitin a macros solve this I guess the first macro would
establish the CSECT allowing me to use in the second macro
.
This is confusing.
I tried it and and generated a value
> On Dec 19, 2023, at 8:17 PM, Tony Thigpen wrote:
>
> Did you ever establish the CSECT name with a CSECT statement before your
> macro?
>
> Tony Thigpen
>
> Joe Reichman wrote on 12/19/23 6:33 PM:
>>2420+
Did you ever establish the CSECT name with a CSECT statement before your
macro?
Tony Thigpen
Joe Reichman wrote on 12/19/23 6:33 PM:
2420+ PRINT ON
50 B240 00E0 2421+ BAKR 14,0
54 51CF 0 2422+
The macro was invoked in the context of unnamed csect However the Macro
established CSECT would having a macro Whitin a macros solve this I guess the
first macro would establish the CSECT allowing me to use in the second
macro
thanks
-Original Message-
From: IBM Mainframe Assembler
MNOTE *,'&=""; &=""'
Also, what do you expect that LAE to do?
Note; you can replace the LA, LA pair with a single LAY; shorter, faster and
clearer.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
2420+ PRINT ON
50 B240 00E0 2421+ BAKR 14,0
54 51CF 0 2422+ LAE 12,0(15,0)
58 41A0 CFFF00FFF 2423+ LA10,4095(,12)
5C 41A0
On Tue, 19 Dec 2023 at 18:12, Joseph Reichman wrote:
> When I use the following
> Using ,12,10
>
> comes up blank even though I know it had been set
> Thanks
>
Available only in a macro. Which makes some sense - what would be its use
in open code? But you say it's blank? If you're in macro
You know what you failed to include in the post.
'nuff said.
On Tue, 19 Dec 2023 18:12:37 -0500 Joseph Reichman
wrote:
:>Hi
:>
:>When I use the following
:> Using ,12,10
:>
:> comes up blank even though I know it had been set
:>Thanks
--
Binyamin Dissen
http://www.dissensoftware.com
Hi
When I use the following
Using ,12,10
comes up blank even though I know it had been set
Thanks
H, C9E2D7D7F0F0F140 is "
ISPP001" (Start of ISPF Log - - - - Session # )
At 02:46 PM 12/19/2023, you wrote:
Yves,
I installed the CAPTURE CLIST and the ISPFHTML load module on a vanilla
z/OS V3R1 system; I get the same S0C1 ABEND.
Digging deeper, the ABEND is caused when
Anyway using MHELP to dump system variables
Tried 71
Just LCLC
Thanks
We're only at 2022-04, I'll have to get our level of HLASM updated.
Thanks,
Robert Ngan
DXC Luxoft
-Original Message-
From: IBM Mainframe Assembler List On Behalf
Of Jonathan Scott
Sent: Tuesday, December 19, 2023 12:42
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Macro variable
Yves,
I installed the CAPTURE CLIST and the ISPFHTML load module on a vanilla
z/OS V3R1 system; I get the same S0C1 ABEND.
Digging deeper, the ABEND is caused when ISPFHTML branches to a x'184'
offset into the TLD, where there is data, not a valid op code. Instead of
the code that ISPFHTML
Robert Ngan writes:
> The ability to do the SETA inside the macro really simplifies our code, but
> it's implementation seem to be somewhat flaky. Sometimes it work, other
> times it get errors.
It doesn't fail with the latest level, and I suspect this might
be a symptom of the problem fixed by
Yves,
Do you have the same display in 2.4?
René
Le mardi 19 décembre 2023 à 17:44:16 UTC+1, Yves Colliard
a écrit :
Bonjour René,
oui je pense que vous avez raison - you could be right... is it documented?
00035000 000183A8 000184A8 000185A8 000186A8 0B4782C8 0135
On 12/19/2023 9:27 AM, Mike Shaw wrote:
Doug used to work in ISPF development at IBM. His code is using knowledge
he had of the TLD format that us mere mortals don't have. Looks like the
TLD may have changed under z/OS V3R1?
Oh no! In our software, we are using a "trick" given to us years ago
Prior to this APAR, I was forced to do the SETA against the equate before the
macro call and then pass the resolved value into the macro i.e.
SETA equ_name
MacroName LEN=
The ability to do the SETA inside the macro really simplifies our code, but
it's implementation seem to be
Yves,
On our z/OS V2R4 system, ISPFHTML does not fail and works as advertised.
You pointed out that upon entry, R1 contains the address of a TLD (Terminal
Logical Descriptor) which is the ISPF control block associated with each
logical screen under ISPF. On my system, ISPFHTML code shortly
Yves,,
IMHO (and I am only a lowly bit fiddler with VSE background)
the problem is this
code in ISPFHTM
47F0F026B OVER_EYECATCHER
21C9E2D7 C6C8E3D4 D340F0F0 F0F2F040 6040C2C1 E2C540D6 E261F3F9
*.00..ISPFHTML 00020 - BASE OS/39*
0976F020 F040D94B F1F0
Bonjour René,
oui je pense que vous avez raison - you could be right... is it documented?
00035000 000183A8 000184A8 000185A8 000186A80B4782C8 0135 E3D3C4F1
00035018 *..cy..dy..ey..fy..bHTLD1..&.*
00035020 00035018 0B495AF0 00035018000429F0 000429D8 000157B0
00015810
25 matches
Mail list logo