I run 60x160 (3279 emulation) -- and on a 14-inch laptop. No problems

-----Original Message-----
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On Behalf Of Farley, Peter
Sent: Friday, 18 November 2022 19:27
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: ASMA500 message question

Why aren't you using a custom size like 50x160?  I use that every day, in
both PCOMM and Vista TN3270.

Mod-5 size is far too small in my opinion -- only 27x132.

I hated the few times I tried to use x3270/wx3270 - totally unintuitive.

Peter

-----Original Message-----
From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> On
Behalf Of Schmitt, Michael
Sent: Friday, November 18, 2022 12:04 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: ASMA500 message question

I can say that I don't use GOFF because it requires LIST(133), which would
be OK except that we run the assembler listings through a program that adds
cross-reference statement numbers to the right side of the listing, which
increases the listing line size. LIST(121) listings are expanded to 133,
which is fine. But GOFF listings are expanded to LRECL=145, which no longer
fits in a mod 5 terminal.

"Every change breaks someone's workflow"


-----Original Message-----
From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> On
Behalf Of Seymour J Metz
Sent: Friday, November 18, 2022 8:32 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: ASMA500 message question

What is your objection to GOFF and XOBJECT?


--
Shmuel (Seymour J.) Metz
https://urldefense.com/v3/__https://clicktime.symantec.com/15uBY2YmhLrGypjCP
f7sX?h=TlrVj6e-jXwm-DUGUoG9J8qy4NZMCDyk1ySgazBSF1Q=&u=http:**Amason.gmu.edu*
*Asmetz3__;Ly8vfg!!Ebr-cpPeAnfNniQ8HSAI-g_K5b7VKg!KJRnahT7X_S-BXawy0OmrVSouS
S3D2vT5awUcmf0051xXsLtd0-OujJ4IzC82YTiuxxjzjO5zzWA0B7Qp5jSe0czWi3eels$ 

________________________________________
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on
behalf of Mike Shaw [quick...@gmail.com]
Sent: Thursday, November 17, 2022 4:03 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: ASMA500 message question

CATTR use requires GOFF object format, which I don't want to use.

Mike


On Thu, Nov 17, 2022 at 3:31 PM Seymour J Metz <sme...@gmu.edu> wrote:

> You need a CATTR with the proper alignment.
>
> ________________________________________
> From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> 
> on behalf of Mike Shaw <techsupp...@quickref.com>
> Sent: Thursday, November 17, 2022 3:20 PM
> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
> Subject: ASMA500 message question
>
> Everyone,
>
> This code fragment:
>
> 00001C 4700 0000            00000    71          NOP   0
> 000020 0101                          72          PR
> 000022                               73          DC    0LQ
> *** ASMA500W Requested alignment exceeds section alignment  *
> 000022                               74 QUAD@1   DC    LQ'0'
>
> causes the *ASMA500W* message to be issued; it's description appears
below:
>
> * ASMA500W Requested alignment exceeds section alignment
>
>   Explanation:  The section alignment is lower than that requested on 
> the  instruction and hence the actual alignment may not be honored.
>
>   System Action:  The requested alignment is ignored.
>
>   Programmer Response:  Change the requested alignment to be less than 
> or  equal to that of the section, or ensure that the desired alignment 
> is  achieved during program linking and loading.
>                                                                        *
> * Severity:  4                  *
>
> Does anyone know what the 'section' mentioned in the message is? Is it 
> a reference to the current control section (CSECT)?
>
> I don't get it...all I want to do is get quadword boundary alignment 
> for the QUAD@1 constant.
>
> Mike Shaw
> MVS/QuickRef Support Group
> Chicago-Soft, Ltd.
>

This message and any attachments are intended only for the use of the
addressee and may contain information that is privileged and confidential.
If the reader of the message is not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
dissemination of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by e-mail
and delete the message and any attachments from your system.


-- 
This email has been checked for viruses by Avast antivirus software.
www.avast.com

Reply via email to