> Could you use __asm() to generate a WXTRN statement?
XLC doesn't allow it:
SMAQ203E Unsupported external symbol type:
> Which XL C? Looking at the compiler ref for 2.4.1, it includes
> #pragma weak (C only)
There's no #pragma weak in SC14-7308-40. What manual were you referencing? I am
on
Rony, that page is wonderful! Thanks. This one is sometimes useful as well:
https://www.cogsci.ed.ac.uk/~richard/utf-8.cgi
every time I go to use it I find the various descriptions a bit confusing (e.g,
Hex code point vs. Hex UTF-8 bytes) but entering a known character makes it
clear.
On May 7, 2023, at 11:41:45, Phil Smith III wrote:
> ...
> This is especially confusing since “plain ol’ ASCII” maps directly to the
> first part of UTF-8-encoded Unicode. This is of course A Good Thing in
> general, but lets people cheat and get away with it—until they don’t.
>
Yup. In
On 07.05.2023 19:41, Phil Smith III wrote:
Seymour J Metz wrote:
I've seen Logical Not () at AA and at AC. Are there and ASCII-based
code pages that have it at a third position? Put another way, is there
a third code point that ooRexx and Regina should recognize as ?
And later:
UTF-8 is just
Seymour J Metz wrote:
>I've seen Logical Not () at AA and at AC. Are there and ASCII-based
>code pages that have it at a third position? Put another way, is there
>a third code point that ooRexx and Regina should recognize as ?
And later:
>UTF-8 is just a transform of Unicode, and the Unicode
On Sun, 7 May 2023 16:12:37 +, Seymour J Metz wrote:
>z/OS 2.5 MVS Programming: Authorized Assembler Services Guide, SA23-1371-50,
>Chapter 31. System REXX, is unclear. Note: I am using the word "environment"
>in the REXXsense rather than generically.
>
>The text lists the environments that
Here is the publication number SA32-0973-50
Here is the code from page 221
*
PUTLINE PARM=PUTBLOK,OUTPUT=(TEXTADS,MULTLIN,DATA), X
MF=(E,IOPLADS)
* PROCESSING
* STORAGE DECLARATIONS
*
ECBADS DS F
IOPLADS DS 4F'0'
TEXTADS DC A(TEXT2) FORWARD POINTER TO THE NEXT LINE.
Please show your code. In particular, what is TERMPUT=?
The term "unprintable" is vague; it depends on the particular character set and
translation table.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List
z/OS 2.5 MVS Programming: Authorized Assembler Services Guide, SA23-1371-50,
Chapter 31. System REXX, is unclear. Note: I am using the word "environment" in
the REXXsense rather than generically.
The text lists the environments that are allowed with TSO=NO, but it does not
list the
On Sun, 7 May 2023 11:33:20 -0400, Joseph Reichman wrote:
>
>I have a couple of PUTLINE questions
>
>first does the MULTLIN,DATA parms When the format is in the way described in
>TSO/E services guide I mean forward chain point length (which includes 4
>bytes for the len + offset ) do a new line
Hi
I have a couple of PUTLINE questions
first does the MULTLIN,DATA parms When the format is in the way described in
TSO/E services guide I mean forward chain point length (which includes 4
bytes for the len + offset ) do a new line break I went so fat as copy the
example in the
UTF-8 is just a transform of Unicode, and the Unicode code point is AC. The
string C2AC is just a way of encoding AC.
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, May 7,
On Sun, 7 May 2023 13:27:16 +, Seymour J Metz wrote:
>I've seen Logical Not (¬) at AA and at AC. Are there and ASCII-based code
>pages that have it at a third position? Put another way, is there a third code
>point that ooRexx and Regina should recognize as ¬?
>
C2AC in UTF-8, which I
I've seen Logical Not (¬) at AA and at AC. Are there and ASCII-based code pages
that have it at a third position? Put another way, is there a third code point
that ooRexx and Regina should recognize as ¬?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
It's not. The exec will always run under the id of the user that started
it. It is exactly the same as running the exec under your own TSO.
ITschak
ITschak Mugzach
*|** IronSphere Platform* *|* *Information Security Continuous Monitoring
for z/OS, x/Linux & IBM I **| z/VM coming soon *
On
No, the barn door is the specific REXX code, not the command to invoke it.
BTW, where is the TSO environment documented for System Rexx? The authorized
Services manual lists supported environments for TSO=NO but not for TSO=YES.
And, yes, "environment" is another overloaded term; it has at
On Sun, 7 May 2023 04:43:27 -0500, Willy Jensen wrote:
>This will issue any TSO command, but security-wise I think it opens a barn
>door.
>
Why is that not cause for an integrity APAR? Wasn't the "barn door"
already open?
>Save it as member TSOCMD in your SYSREXX lib.
>
>/* general TSO command
Hi Willy,
In TSO (unlike PGM=IDCAMS), "EN" is sufficient.
Regards,
David
On 2023-05-07 05:43, Willy Jensen wrote:
This will issue any TSO command, but security-wise I think it opens a barn door.
Save it as member TSOCMD in your SYSREXX lib.
/* general TSO command rexx */
This will issue any TSO command, but security-wise I think it opens a barn door.
Save it as member TSOCMD in your SYSREXX lib.
/* general TSO command rexx */
address tso arg(1)
Exit 0
Sample use (@ is my SYSREXX command char):
@TSOCMD LISTCAT
19 matches
Mail list logo
