Thanks Jonathan,
I'll ask our support department to install this APAR.
Fred!
-Original Message-
From: IBM Mainframe Assembler List On Behalf
Of Jonathan Scott
Sent: maandag 20 april 2020 9:54
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: CL8''
> Does anybody know why this happens:
a hex editor.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Windt, W.K.F. van der (Fred)
[0782fe4a8c02-dmarc-requ...@listserv.uga.edu]
Sent: Monday, April
(NOLIMIT,MAP,WARN(15))
NOWORKFILE
XREF(SHORT,UNREFS)
No Overriding DD Names
-Original Message-
From: IBM Mainframe Assembler List On Behalf
Of Windt, W.K.F. van der (Fred)
Sent: maandag 20 april 2020 9:32
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re
: CL8''
There is nothing wrong with CL8''.
I guess &RQS has a value.
//Mikael
-Original Message-
From: IBM Mainframe Assembler List On Behalf
Of Windt, W.K.F. van der (Fred)
Sent: den 20 april 2020 08:24
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: CL8'&#x
Hi,
Does anybody know why this happens:
Active Usings: None
R-Loc Object CodeAddr1 Addr2 Stmt Source Statement
HLASM R6.0 2020/04/20 08.13
00 0A00404040401938 DCCL8''
08 40404040404040401939 DC
> It surprises me that no one has pointed out that having complex tables
> assembled/compiled into a program is generally a Bad Idea. Almost always
> such tables have to be updated and that tends to require a programmer,
> rather than anyone with a text editor, if the tables are read into storage a
> > Except that he wanted the literal "pooling" that the assembler's logic
> > provides: if you code =X'1234' twice, you only get one X'1234' literal.
> > Apparently he has a LOT of literal data.
> >
> > Charles
>
> If that's really necessary, one could use a SETC array to track the values
> define
> Except that he wanted the literal "pooling" that the assembler's logic
> provides: if you code =X'1234' twice, you only get one X'1234' literal.
> Apparently he has a LOT of literal data.
We use these structures to describe mappings from records to XML or JSON. The
literals are fieldnames and n
> This is really a simple problem to solve. Here is a sample "data" program
> that
> I believe satisfies the OP's needs:
>
> MACRO
> &LBL LITADCON &LIT
> DATAAREA LOCTR ,
> L&SYSNDX DC&LIT
> &SYSECT LOCTR ,
> &LBL DCA(L&SYSNDX)
> MEND
> TESTPGM CSECT ,
> DATAP
> IMHO the right place for the sequence numbers is 1970.
>
> Charles
:)
Fred!
-
ATTENTION:
The information in this e-mail is confidential and only meant for the intended
recipient. If you are not the intended recipient, don't use o
> I don't know why I keep thinking about this but I believe I have a solution.
> It
> will give you exactly what you wanted, effectively DC A(=literal). It is a
> hack
> and a kludge and I would not do it myself, but I believe it will work.
>
> A. Add a separate CSECT to your code following the
> Is there some reason you can't just imbed the value in the structure, instead
> of introducing a level of indirection? I could see using pointers for
> variable-
> length strings, but the examples all show a 4-byte constant.
Ah, then the example was unfortunate: because those literals are poin
> > Really no better than what I suggested below, but for some reason I
> > find the following approach amusing.
> >
> > The OP's original plan was to include
> >
> > LABEL DC A(=x'123')
> >
> > in his table and then, presumably
> >
> > L Rn,LABEL
> >
> > in his executable code. Almost exactl
> If S-constants will work for you, then you can fake them with pseudo-
> executable instructions. Instead of
>
> DC A(=X'123')
>
> Generate
>
> L 0,=X'123'
>
> If you have a USING for R0 on your literal pool, then the above will generate
> a 4-byte instruction. Ignore the first two bytes, and the
> It is illogical that this does not work but that is the way it is.
>
> Do S-constants work? That is, is S(=x'123') valid, and might that work for
> you?
>
> Do you have to use literals? Can you use named constants instead?
>
> Charles
The S-constants seem to have the same limitation:
006
> It is illogical that this does not work but that is the way it is.
>
> Do S-constants work? That is, is S(=x'123') valid, and might that work for
> you?
>
> Do you have to use literals? Can you use named constants instead?
>
> Charles
I have this issue in a set of macro's that generate a data s
> On 08/12/17 07:39, Windt, W.K.F. van der (Fred) wrote:
> > Right now I am using two LOCTRs and generated labels to generate
> > pointers in the data structure (the first LOCTR) to the literals in a
> > separate area (the second LOCTR). But that means that every literal is
> to get what you want I would resort to this:
>
> ACONST DC A(*+4),X'00FF4711')
>
> or you could use LA R,=X'00FF4711'
> instead of L R,ACONST
Hi Martin,
Thanks for the suggestion but my problem is that I am generating a data
structure. The DC A(...) needs to generate the address of that liter
Hello,
I want to generate a constant with the four byte of a literal in the literal
pool. I naively coded this:
DCA(=X'00029983')
Hoping to get the literal X'00029983' in the literal pool and a four byte
address of that literal out of the DC instruction but instead I get this error
messa
19 matches
Mail list logo
