Ref: Your note of Mon, 9 Jan 2023 12:54:05 -0500
Joseph Reichman wrote:
> I have zdpt personal edition licensce can I report this
> I mean I can open a ticket and in the comments have them assign it to you
> I can upload my sysadata to the ticket opened
We do not know what level of technical su
I have zdpt personal edition licensce can I report this
I mean I can open a ticket and in the comments have them assign it to you
I can upload my sysadata to the ticket opened
> On Jan 9, 2023, at 12:38 PM, Jonathan Scott
> wrote:
>
> Ref: Your note of Mon, 9 Jan 2023 12:21:58 -0500
>
Ref: Your note of Mon, 9 Jan 2023 12:21:58 -0500
Joseph Reichman wrote:
> Just to let you know I searched the sysadata
> For M_WSA and there was only a source record type 30
>
> There were no type 20 records
The same information should also be present in the ESD report in
the listing, before th
Just to let you know I searched the sysadata
For M_WSA and there was only a source record type 30
There were no type 20 records
The code was compiled under z/os 2.4 I’m now running z/os 2.5 B version ADCD
I have zdpt personal edition
> On Jan 9, 2023, at 11:24 AM, Jonathan Scott
> wrote:
The fact that the alignment warning appears confirms that the
CATTR statement was processed. The warning is due to a known
bug in the C compiler which may well be fixed in the latest
level, and should be harmless in that it does not affect the
generated code.
I'd expect to see M_WSA among the ele
These were my parms
No Overriding ASMAOPT Parameters
Overriding Parameters- OBJ,ADATA,SYSPARM(DEBUG),GOFF
No Process Statements
Joseph Reichman wrote:
> I just compiled a Metal C program and generated sysadata
>
> I see a number CATTR assembler instructions
> There are 0030 records but I dont see 0020 external symbol
> records for the CATTR
CATTR normally generates an element definition (ED, 03) ESD
entry for the specifie
