Re: ASMA500 message question

2022-11-19 Thread Pieter Wiid
: IBM Mainframe Assembler List 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

Re: ASMA500 message question

2022-11-18 Thread Seymour J Metz
Most session managers support D4C32XX3 if properly configured. From: IBM Mainframe Assembler List on behalf of Schmitt, Michael Sent: Friday, November 18, 2022 2:36 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: ASMA500 message question With any

Re: ASMA500 message question

2022-11-18 Thread Seymour J Metz
2022 2:06 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: ASMA500 message question Ha, I knew someone would ask that! It is because non-standard logmodes are incompatible with our VTAM session management system, that allows for multiple sessions within one terminal. But why not just open

Re: ASMA500 message question

2022-11-18 Thread Dave Clark
"IBM Mainframe Assembler List" wrote on 11/18/2022 02:36:30 PM: > With any larger terminal size our session manager uses logmode > D4C32XX3 (vs. SNX32705 for mod 5). I can override that, but that's > the logmode that works for non-standard terminals. > > In single-session 62x160 works. In mult

Re: ASMA500 message question

2022-11-18 Thread Schmitt, Michael
ubject: Re: ASMA500 message question "IBM Mainframe Assembler List" wrote on 11/18/2022 02:06:46 PM: > Ha, I knew someone would ask that! > > It is because non-standard logmodes are incompatible with our VTAM > session management system, that allows for multiple sessions with

Re: ASMA500 message question

2022-11-18 Thread Dave Clark
"IBM Mainframe Assembler List" wrote on 11/18/2022 02:06:46 PM: > Ha, I knew someone would ask that! > > It is because non-standard logmodes are incompatible with our VTAM > session management system, that allows for multiple sessions within > one terminal. 62x160 is a standard logmode (for

Re: ASMA500 message question

2022-11-18 Thread Schmitt, Michael
Mainframe Assembler List On Behalf Of Farley, Peter Sent: Friday, November 18, 2022 11:27 AM 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

Re: ASMA500 message question

2022-11-18 Thread Steve Smith
Well, you don't need GOFF for your limited purpose. I'm pretty sure SECTALGN(16) works without it. If that's a problem, then you'll have to decide what option's least painful for you. sas On Fri, Nov 18, 2022 at 12:04 PM Schmitt, Michael wrote: > I can say that I don't use GOFF because it req

Re: Subject: ASMA500 message question

2022-11-18 Thread Jonathan Scott
Quadword alignment using SECTALGN(16) is supported with OBJ if you are linking on z/OS, using the Binder. It uses special ESD type codes for quadword aligned sections. As it is not always supported, specifying it with OBJ will produce warning ASMA216W, which can be suppressed using SUPRWARN(216).

Re: ASMA500 message question

2022-11-18 Thread Farley, Peter
frame Assembler List 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

Re: ASMA500 message question

2022-11-18 Thread Schmitt, Michael
: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://clicktime.symantec.com/15uBY2YmhLrGypjCPf7sX?h=TlrVj6e-jXwm-DUGUoG9J8qy4NZMCDyk1ySgazBSF1Q=&u=http

Re: Subject: ASMA500 message question

2022-11-18 Thread Charles Mills
mbler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Peter Relson Sent: Friday, November 18, 2022 4:51 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Subject: ASMA500 message question You ignore the message at your own risk. Unless your module is page-aligned and this is a page-aligned CSECT w

Re: ASMA500 message question

2022-11-18 Thread Mike Shaw
__ > 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 objec

Re: ASMA500 message question

2022-11-18 Thread Seymour J Metz
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 wrote: > You need a CATTR with the proper a

Re: Subject: ASMA500 message question

2022-11-18 Thread Keith Moe
Nucleus. Keith Sent from an iPhone > On Nov 18, 2022, at 09:50, Peter Relson wrote: > > You ignore the message at your own risk. > > Unless your module is page-aligned and this is a page-aligned CSECT within > that module, you have no idea if the CSECT will land on a quadword (or > stronge

Re: Subject: ASMA500 message question

2022-11-18 Thread Mike Shaw
On Fri, Nov 18, 2022 at 7:50 AM Peter Relson wrote: > > Why would you not want to use GOFF? I can think of only one module in all > of z/OS that cannot use GOFF. I'll let guesses occur before providing the > answer in a day or two. > > Fear of the unknown! I will try it. Mike S.

Re: Subject: ASMA500 message question

2022-11-18 Thread Peter Relson
You ignore the message at your own risk. Unless your module is page-aligned and this is a page-aligned CSECT within that module, you have no idea if the CSECT will land on a quadword (or stronger) boundary. And if you truly need quadword boundary and don't have it, things won't end well. Mike

Re: ASMA500 message question

2022-11-17 Thread Mike Shaw
based on SECTALGN and the warning is > i>ssued if item alignment exceeds the binder section alignment. > > -Original Message- > From: IBM Mainframe Assembler List On > Behalf Of Mike Shaw > Sent: Thursday, November 17, 2022 4:04 PM > To: ASSEMBLER-LIST@LISTSER

Re: ASMA500 message question

2022-11-17 Thread Mike Hochee
17, 2022 4:04 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: ASMA500 message question Caution! This message was sent from outside your organization. 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 wrote: >

Re: ASMA500 message question

2022-11-17 Thread Mike Shaw
of Mike Shaw > Sent: Thursday, November 17, 2022 3:20 PM > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: ASMA500 message question > > Everyone, > > This code fragment: > > 1C 4700 071 NOP 0 > 20 0101 72

Re: ASMA500 message question

2022-11-17 Thread Seymour J Metz
You need a CATTR with the proper alignment. From: IBM Mainframe Assembler List on behalf of Mike Shaw Sent: Thursday, November 17, 2022 3:20 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: ASMA500 message question Everyone, This code fragment: 1C

Re: ASMA500 message question

2022-11-17 Thread Dave Clark
"IBM Mainframe Assembler List" wrote on 11/17/2022 03:20:36 PM: > I don't get it...all I want to do is get quadword boundary alignment for > the QUAD@1 constant. I would use the CNOP instruction, instead. Sincerely, Dave Clark -- int.ext: 91078 direct: (937) 531-6378 home: (937) 751-3

ASMA500 message question

2022-11-17 Thread Mike Shaw
Everyone, This code fragment: 1C 4700 071 NOP 0 20 0101 72 PR 22 73 DC0LQ *** ASMA500W Requested alignment exceeds section alignment * 22