Scott,
you are asking this question on an assembler list. I do not dare to
answer althru there are various codepages for various purposes on VM -
VSE or MVS (CICS, LE, HLASM, COBOL, z/PDT UR-input/outputhandling)
OR are you asking this question in a Linux context?
My linux runs on almost
Look on pp. 7-39ff of the current PrOp. If you google use the search argument
'CIPHER MESSAGE WITH CHAINING (KMC)'.
KMx is really a set of instructions. The particular element of this
set that is to be executed is specified (but not uniquely) by the
function-code value,
o 0, for KM-Query,
o
John,
Ty my friend loved it ..knew what it was but not how it really worked...much
appreciated
Regards,
Scott ford
www.identityforge.com
from my IPAD
'Infinite wisdom through infinite means'
On Nov 21, 2013, at 10:26 AM, John McKown john.archie.mck...@gmail.com
wrote:
I haven't seen
All,
Is there a way I can query what ccsids a system is running using a API of some
sort or even in native assembler ?
Scott ford
www.identityforge.com
from my IPAD
'Infinite wisdom through infinite means'
Here economy of means would lead me to prefer an SRST to Jon
Perryman's traditional approach, which searches for a delimiter or
delimiters using a TRT[E].
Just where the break point is depends upon how many delimiters are
being searched for concurrently. When, as here, it is a single
character
John
Ty kind sir I saw it ..looks like what I want
Scott ford
www.identityforge.com
from my IPAD
'Infinite wisdom through infinite means'
On Nov 21, 2013, at 1:07 PM, John McKown john.archie.mck...@gmail.com wrote:
Ref:
There's no problem with having an inline targe for the EX instruction. It's
used regularly by at least 1 ISV. The instruction get's executed twice but the
second time has the instructions and data already in the pipe. I wonder if the
second instruction fetch offsets the second execution of the
John, all
Yes, I was really referring to the mainframe assembler that came with MVS
3.8 which is not HLASM. I believe the MVS 3.8 assembler only supported 24
bit addressing like MVS 3.8. I've never really used Hercules so I'm not
certain.
z390 supports 32 bit addressing, and is designed to be
On 21/11/2013 20:26, Don Higgins wrote:
John, all
Yes, I was really referring to the mainframe assembler that came with MVS
3.8 which is not HLASM. I believe the MVS 3.8 assembler only supported 24
bit addressing like MVS 3.8. I've never really used Hercules so I'm not
certain.
That is
Ref:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2UNA1/CCONTENTS
Unicode System Services
z/OS UNIX iconv command:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/BPXZA5C0/ICONV
C language iconv support:
I looked for the KM instruction. Our quickref does not list it, and when I do
a google I see nothing of value. Can you explain it? Thanks.
On Wed, 11/20/13, Automatic digest processor lists...@listserv.uga.edu wrote:
Subject: ASSEMBLER-LIST Digest
I haven't seen this referenced here. It is a rather basic overview of
millicode, but I hope it will be of interest to others too. Perhaps someone
who is just getting into assembler.
ftp://public.dhe.ibm.com/s390/zos/racf/pdf/ny_metro_naspa_2012_10_what_and_why_of_system_z_millicode.pdf
.
--
On 11/21/2013 10:34 AM, Tony Harminc wrote:
SRST has been around for much longer than that; it certainly long
predates z architecture. So it is quite safe in any real world
scenario to assume that the instruction is available.
SRST and the other string instructions were available on early
At 06:31 -0800 on 11/21/2013, Jon Perryman wrote about Re: Moves and others:
There's no problem with having an inline targe for the EX
instruction. It's used regularly by at least 1 ISV. The instruction
get's executed twice but the second time has the instructions and
data already in the pipe.
I'm currently out of the office..
...and will return to the office on Monday, November 25th.
If you need assistance before then, one of my colleagues may be able to assist.
Feel free to contact them using the @CTO Env Eng - Mainframe distribution list
Thanks,
Bob R
This is some of the original code, which now works. Also experimenting with
the
other suggestions, for learning purposes.
R8 is holding the variable number of bytes (length of 1-8). The move below is
working.
Ran test data from 1-8 characters long, and it worked fine. The other move
When searching a variable length number of bytes, one must also take care that
one does not advance the pointer too far and attempt to access storage that is
not part of the input buffer being searched.
Bill Fairchild
Franklin, TN
- Original Message -
From: pw...@mweb.co.za
To:
17 matches
Mail list logo
