On Sun, 22 Jan 2012 14:33:51 GMT "esst...@juno.com" wrote:
:>Is there a difference in Cross Memory performance when calling a PC routine
that is a Space Switching routine vs a Non Space Switching Routine.
One would thinks so, as a SS-PC requires loading a new PASN and STO and the
validation req
Paul
I would imagine there is very little performance overhead difference calling
PC-ss rather than PC-cp - maybe the only difference(s) being any AT lookup or
ETCON for non-system LX.
Normally, PC-ss routines access and/or manipulate control block structures in
the cross-memory server address
I am out of the office until 01/25/2012.
I will be out of the office. If you needed to contact me call me on my cell
phone, at home and/or email me too.
Note: This is an automated response to your message "Re: PC-SS vs PC-CP
Curiosity" sent on 1/23/2012 7:05:55 AM.
This is the only notificatio
I suggest that performance not be the consideration you should care about
here (even if there is a small difference; I do not happen to know if
there is). The main consideration should be your being considerate with
respect to customer needs -- using common storage when it is not needed
can be detr
Hello David,
ASMA033I with RC=000 goes back to at least HLASM R3, so no recent changes
are apparent.
ASMA213W (same message text as 033I) with RC=004 was introduced with APAR
PQ39602 in HLASM R3, but only in the case where:
a) Operands are the target of a branch yet have an odd-byte
alig
As I have mentioned, I've been writing some HLASM based UNIX programs for
"fun", not "profit". Well, UNIX likes some non-printable control characters
quite a bit. In particular, the TAB (x'05') and NewLine (x'15'). I the past, I
have used ISPF edit, done a "hex on" and inserted the hex values ne
John,
The classical way to introduce non-printing, no-grapheme characters
into an assembly-language program is to use the BYTE bif, as in
|&nul setc BYTE(0) --nul character, x'00'
The argument of the BYTE bif is a character-set code point or rank r,
0 <= r <= 255.
--jg
On 1/
Thanks! I didn't see that one.
--
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john.mck...@healthmarkets.com * www.HealthMarkets.com
Confidentiality Notice: This e-mail message may cont
On 1/23/2012 1:41 PM, McKown, John wrote:
As I have mentioned, I've been writing some HLASM based UNIX programs for "fun", not "profit". Well, UNIX
likes some non-printable control characters quite a bit. In particular, the TAB (x'05') and NewLine (x'15'). I the past, I have
used ISPF edit, don
On 1/23/2012 2:27 PM, Steve Comstock wrote:
I prefer to just code something like:
PrintLine DC C'This line is printed to "stdout".',x'15'
But, of course, you need to watch for length attributes
if you move or print or otherwise manipulate this; that
is L'PrintLine will not include the one byte
During edit, I use rarely used characters like ¢ (the cent sign) as a place
holder and just before saving I issue C ALL ¢ x'15 to produce the desired
hex value.
:>: -Original Message-
:>: From: IBM Mainframe Assembler List [mailto:ASSEMBLER-
:>: l...@listserv.uga.edu] On Behalf Of McKown,
We all find other people's notions of what constitutes good programming drôle.
I disapprove, very strongly, of scattering magic numbers in source
code. I also exploit the the availability of set symbols in open
code, using them almost to the exclusion of equates. (I do use
register equates, bec
Your reasoning is better than mine. I don't want "magic numbers" or hex
in my code because I use the z/OS UNIX "vi" on occasion to do a fast
edit. And it does not like embedded NLs. It thinks (rightly) that they
indicate the end of a line. And so does the "as" command, which I use
via a makefile to
13 matches
Mail list logo
